Triple
T35936627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordanian Turkmen |
E1039322
|
entity |
| Predicate | hasNoSovereignState |
P111660
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jordanian Turkmen, hasNoSovereignState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSovereignState Context triple: [Jordanian Turkmen, hasNoSovereignState, true]
-
A.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
B.
hasNoSovereignOwnershipRecognized
chosen
Indicates that no entity is acknowledged as having sovereign ownership or supreme legal authority over the subject.
-
C.
hasNoPermanentSettlements
Indicates that the subject does not maintain any long-term or stable inhabited locations.
-
D.
notSovereignTerritory
Indicates that a location or region is not recognized as an independent sovereign territory under its own full governmental authority.
-
E.
isNonSovereign
Indicates that an entity lacks full independent governing authority and is subject to the sovereignty of another state or higher political authority.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.