Triple
T37290791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirs of Hunza |
E925659
|
entity |
| Predicate | lostAutonomyYear |
P34727
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Mirs of Hunza, lostAutonomyYear, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostAutonomyYear Context triple: [Mirs of Hunza, lostAutonomyYear, 1974]
-
A.
gainedAutonomyFrom
Indicates that one entity obtained independence or self-governing control from another entity that previously held authority over it.
-
B.
lostStatehoodInYear
Indicates that an entity ceased to be a recognized state or lost its statehood in the specified year.
-
C.
lostAuthorityInYear
Indicates that an entity ceased to hold or exercise a particular authority in the specified year.
-
D.
hadAutonomyUntil
chosen
Indicates that an entity possessed a certain degree of self-governance or independent decision-making authority up to a specific point in time, after which that autonomy ceased or was reduced.
-
E.
lostIndependenceIn
Indicates that an entity ceased to be politically or administratively independent in a specified place or under a specified jurisdiction.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.