Triple
T30714378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ulaş |
E781981
|
entity |
| Predicate | hasSovereignCommander |
P1197
|
FINISHED |
| Object | Sultan Mustafa II |
E210819
|
NE 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: Sultan Mustafa II | Statement: [Battle of Ulaş, hasSovereignCommander, Sultan Mustafa II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovereignCommander Context triple: [Battle of Ulaş, hasSovereignCommander, Sultan Mustafa II]
-
A.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
C.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
D.
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.
-
E.
commanderCountry
Indicates that a person serving as a commander is associated with or represents a specific country in that commanding role.
- F. None of above.
Provenance (4 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292af34ce08190b1dc55c46d00cc94 |
completed | June 10, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 29, 2026, 8:35 p.m.