Triple
T3253819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raza Sahib |
E68249
|
entity |
| Predicate | roleInSiegeOfArcot |
P28183
|
FINISHED |
| Object | commander of attacking forces |
—
|
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: commander of attacking forces | Statement: [Raza Sahib, roleInSiegeOfArcot, commander of attacking forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSiegeOfArcot Context triple: [Raza Sahib, roleInSiegeOfArcot, commander of attacking forces]
-
A.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
garrisonSide
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
-
C.
roleDuringConquest
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
D.
roleInMexicanAmericanWar
Indicates that an entity participated in the Mexican–American War in a specified capacity or function.
-
E.
garrisonCommander
Indicates that one entity serves as the commanding officer in charge of the military garrison located at or associated with 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf640fd8819083c3c0cc41db2ffc |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.