Triple
T25442817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akkoyunlu |
E637550
|
entity |
| Predicate | UzunHasan_role |
P158522
|
FINISHED |
| Object | most powerful ruler of Akkoyunlu |
—
|
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: most powerful ruler of Akkoyunlu | Statement: [Akkoyunlu, UzunHasan_role, most powerful ruler of Akkoyunlu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UzunHasan_role Context triple: [Akkoyunlu, UzunHasan_role, most powerful ruler of Akkoyunlu]
-
A.
ZawiszaRole
Indicates that an entity holds or is assigned a specific role or function within the Zawisza context.
-
B.
HarrisonRole
Indicates that an entity holds, has held, or is associated with a specific role or position in relation to Harrison.
-
C.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
-
D.
hasHumanCharacterRole
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
-
E.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
- F. None of above. chosen
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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7016534819084f239f3cf901411 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2 p.m.