Triple
T26583727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yıldırım Akbulut |
E667147
|
entity |
| Predicate | wasPredecessor |
P97
|
FINISHED |
| Object | Mesut Yılmaz |
—
|
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: Mesut Yılmaz | Statement: [Yıldırım Akbulut, wasPredecessor, Mesut Yılmaz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPredecessor Context triple: [Yıldırım Akbulut, wasPredecessor, Mesut Yılmaz]
-
A.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
B.
predecessorAsDeFactoRuler
Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
-
C.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorAsLocalRuler
Indicates that one entity previously held the position of local ruler immediately before another entity in a given domain or territory.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614e3b09c81908ee0b323578c6883 |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:04 a.m.