Triple
T32741093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dersim |
E837221
|
entity |
| Predicate | previousAuthority |
P12937
|
FINISHED |
| Object | Ottoman Empire |
—
|
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: Ottoman Empire | Statement: [Dersim, previousAuthority, Ottoman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAuthority Context triple: [Dersim, previousAuthority, Ottoman Empire]
-
A.
subsequentAuthority
Indicates that one authority or decision follows and is derived from, or dependent on, a prior authority or decision in a sequence.
-
B.
primaryAuthorityFor
Indicates that one entity serves as the main or leading source of control, responsibility, or decision-making power for another entity or domain.
-
C.
previousAdministrator
chosen
Indicates that one entity formerly held an administrative role or position over another entity before the current administrator.
-
D.
previouslyAuthorizedBy
Indicates that an action, access, or decision was granted or approved earlier by a specified entity or authority.
-
E.
previousGoverningBody
Indicates that one governing body served in authority immediately before another specified governing body.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 1, 2026, 1:12 a.m.