Triple
T33844001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavelua (King of Uvea) |
E867427
|
entity |
| Predicate | governsTraditionalDistrict |
P27698
|
FINISHED |
| Object | Uvea |
—
|
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: Uvea | Statement: [Lavelua (King of Uvea), governsTraditionalDistrict, Uvea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTraditionalDistrict Context triple: [Lavelua (King of Uvea), governsTraditionalDistrict, Uvea]
-
A.
electionDistrict
Indicates that one entity is the electoral district or constituency in which another entity (such as a voter, candidate, or election event) is situated or to which it is assigned.
-
B.
servedDistrict
chosen
Indicates that an entity has provided official service or representation to a particular district.
-
C.
electoralDistrictIncludes
Indicates that a given electoral district geographically contains or encompasses a specified area or location.
-
D.
servesGovernmentDistrict
Indicates that an entity provides official services or representation to a specific government district.
-
E.
congressionalDistrict
Indicates that one entity is a congressional district that politically represents or geographically contains the other entity.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: May 1, 2026, 1:47 a.m.