Triple
T2543340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Assaye |
E57837
|
entity |
| Predicate | describedAsByWellesley |
P37427
|
FINISHED |
| Object | his finest battle |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: his finest battle | Statement: [Battle of Assaye, describedAsByWellesley, his finest battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsByWellesley Context triple: [Battle of Assaye, describedAsByWellesley, his finest battle]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
officiallyDescribedAs
Indicates that an entity is formally characterized or defined using a specific description in an official or authoritative context.
-
D.
laterDescribedAs
chosen
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
E.
isDescriptive
Indicates that one entity provides a description or characterization of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bf6cac819083a9ab9d041d8641 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.