Triple
T11406955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Landen |
E270261
|
entity |
| Predicate | AlliedCommanderTitle |
P2084
|
FINISHED |
| Object | King of England |
—
|
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: King of England | Statement: [Battle of Landen, AlliedCommanderTitle, King of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlliedCommanderTitle Context triple: [Battle of Landen, AlliedCommanderTitle, King of England]
-
A.
overallAlliedCommander
Indicates that one entity serves as the highest-ranking commander with ultimate authority over all allied forces associated with the other entity.
-
B.
commanderTitle
chosen
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
D.
admiralOfFleet
Indicates a relationship where a person holds the highest naval rank or command position over an entire fleet.
-
E.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014c820c81908538ba4a08e13230 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.