Triple
T31762157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peiwar Kotal |
E810708
|
entity |
| Predicate | commanderInBattle |
P68449
|
FINISHED |
| Object | Frederick Roberts |
—
|
NE NERFINISHED |
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: Frederick Roberts | Statement: [Peiwar Kotal, commanderInBattle, Frederick Roberts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderInBattle Context triple: [Peiwar Kotal, commanderInBattle, Frederick Roberts]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
commanderOfVictoriousSide
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to another entity.
-
C.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
D.
commanderInChiefDuringWar
Indicates that one entity served as the highest-ranking military leader (commander in chief) of another entity for the duration of a specified war.
-
E.
sideCommander
chosen
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 30, 2026, 11:31 p.m.