Triple
T28832360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian-Ottoman conflicts |
E728083
|
entity |
| Predicate | hasRulerDuringPhase |
P169288
|
FINISHED |
| Object | Sultan Abdulhamid II |
—
|
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: Sultan Abdulhamid II | Statement: [Armenian-Ottoman conflicts, hasRulerDuringPhase, Sultan Abdulhamid II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerDuringPhase Context triple: [Armenian-Ottoman conflicts, hasRulerDuringPhase, Sultan Abdulhamid II]
-
A.
hasEarlyPhaseRuler
Indicates that an entity served as a ruler during the early phase or initial period of another entity's existence or development.
-
B.
rulerDuringConstruction
Indicates that a particular person held ruling authority over a place or polity during the time a specific construction project was carried out.
-
C.
hasFirstRuler
Indicates that an entity has another entity as its earliest or original ruler.
-
D.
hasSignificantRuler
Indicates that an entity has or had a ruler whose leadership is considered historically or contextually important.
-
E.
hasRulerCharacter
Indicates that a ruler possesses a particular character trait or quality.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 6:38 a.m.