Triple
T13447138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadadli |
E320511
|
entity |
| Predicate | hasSovereignStateIndependenceYear |
P595
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Wadadli, hasSovereignStateIndependenceYear, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovereignStateIndependenceYear Context triple: [Wadadli, hasSovereignStateIndependenceYear, 1981]
-
A.
partOfIndependentStateSince
Indicates that an entity has been a constituent part of an independent state starting from a specified point in time.
-
B.
lastTrustTerritoryIndependenceYear
Indicates the year in which the last remaining trust territory associated with an entity achieved independence.
-
C.
independenceYear
chosen
Indicates the year in which an entity achieved political independence or was formally recognized as independent.
-
D.
hasIndependence
Indicates that an entity possesses or has achieved political, legal, or functional independence from another controlling authority.
-
E.
independenceDeclaredFrom
Indicates that one entity has formally declared its independence from another entity, ending or rejecting the latter’s authority or control.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef758b08190b9aa5ec7082cd417 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.