Triple
T27242761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okoa |
E687252
|
entity |
| Predicate | belongsToMonarchy |
P18474
|
FINISHED |
| Object | Kingdom of 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: Kingdom of Tonga | Statement: [Okoa, belongsToMonarchy, Kingdom of Tonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToMonarchy Context triple: [Okoa, belongsToMonarchy, Kingdom of Tonga]
-
A.
associatedWithMonarchy
chosen
Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
-
B.
associatedWithMonarch
Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
-
C.
associatedWithMonarchyType
Indicates that an entity has a connection or relevance to a particular type or form of monarchy.
-
D.
childOfMonarch
Indicates that one entity is the offspring (biological or legally recognized) of another entity who holds or held the status of monarch.
-
E.
refersToMonarchOf
Indicates that one entity makes reference to, mentions, or designates the reigning monarch of a specified realm or polity.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 10:39 a.m.