Triple
T33843978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavelua (King of Uvea) |
E867427
|
entity |
| Predicate | isHighestTraditionalAuthorityOf |
P70686
|
FINISHED |
| Object | Wallis Island |
—
|
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: Wallis Island | Statement: [Lavelua (King of Uvea), isHighestTraditionalAuthorityOf, Wallis Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighestTraditionalAuthorityOf Context triple: [Lavelua (King of Uvea), isHighestTraditionalAuthorityOf, Wallis Island]
-
A.
hasSovereignAuthority
Indicates that one entity holds ultimate governing or ruling power over another entity or domain.
-
B.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
-
C.
sovereigntyHolder
Indicates which entity possesses ultimate governing authority or sovereign control over another entity or territory.
-
D.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
E.
hasSovereignPowerOver
chosen
Indicates that one entity holds ultimate governing authority or supreme ruling power over another 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_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.