Triple
T20446649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izz al-Din Kaykaus I |
E501532
|
entity |
| Predicate | soughtControlOver |
P69335
|
FINISHED |
| Object | trade routes in Anatolia |
—
|
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: trade routes in Anatolia | Statement: [Izz al-Din Kaykaus I, soughtControlOver, trade routes in Anatolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtControlOver Context triple: [Izz al-Din Kaykaus I, soughtControlOver, trade routes in Anatolia]
-
A.
aimsToControl
chosen
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
B.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
C.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
D.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
E.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cfe57a8819094bd3d324bd567f5 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.