Triple
T31323895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Otlukbeli |
E798826
|
entity |
| Predicate | primaryOttomanLeader |
P23718
|
FINISHED |
| Object | Mehmed II |
E20847
|
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: Mehmed II | Statement: [Battle of Otlukbeli, primaryOttomanLeader, Mehmed II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOttomanLeader Context triple: [Battle of Otlukbeli, primaryOttomanLeader, Mehmed II]
-
A.
OttomanCommander
chosen
Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
-
B.
OttomanDynasty
Indicates a dynastic or ruling-family relationship associated with the Ottoman Empire.
-
C.
OttomanRole
Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
-
D.
OttomanName
Indicates that an entity has a name or designation used during the Ottoman Empire period.
-
E.
predecessorAsKapudanPasha
Indicates that one entity previously held the office of Kapudan Pasha (Grand Admiral of the Ottoman Navy) immediately before the other entity.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a720d100c8190b74f17e6cf272013 |
completed | June 11, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.