Triple
T27803371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esia |
E702306
|
entity |
| Predicate | locatedInPolity |
P159632
|
FINISHED |
| Object | Tonga |
—
|
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: Tonga | Statement: [Esia, locatedInPolity, Tonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPolity Context triple: [Esia, locatedInPolity, Tonga]
-
A.
politicallyLocatedIn
Indicates that an entity is situated within or belongs to a particular political or administrative jurisdiction or territory.
-
B.
positionInPolity
Indicates that one entity holds a specific official role, office, or position within a particular political or governmental organization.
-
C.
isInPolity
chosen
Indicates that one entity is located within, belongs to, or falls under the jurisdiction of a particular political unit or governing authority.
-
D.
locatedInGovernmentBody
Indicates that an entity is situated within, or is part of, a specific governmental body or institution.
-
E.
locatedInSubnationalEntity
Indicates that one entity is geographically or administratively situated within a specific subnational division, such as a state, province, or region.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: April 27, 2026, 5:36 p.m.