Triple
T17709048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | independence of Tuvalu |
E441512
|
entity |
| Predicate | politicalStatusAfter |
P86247
|
FINISHED |
| Object | sovereign state |
—
|
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: sovereign state | Statement: [independence of Tuvalu, politicalStatusAfter, sovereign state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusAfter Context triple: [independence of Tuvalu, politicalStatusAfter, sovereign state]
-
A.
politicalStatusAfterEvent
chosen
Indicates the political status or condition an entity holds as a result of, or following, a specific event.
-
B.
politicalStatusBefore
Indicates the political status or condition an entity held prior to a specified event, change, or reference point.
-
C.
politicalStatusAtEnd
Indicates the political status or condition an entity holds at the conclusion of a specified event or time period.
-
D.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
E.
politicalStatusVariation
Indicates a change or difference in an entity’s political status over time or across contexts.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47299cd7881908aac13b84acb61f7 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.