Triple
T38412867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uvea Island |
E901524
|
entity |
| Predicate | hasTraditionalMonarchy |
P95806
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Uvea Island, hasTraditionalMonarchy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalMonarchy Context triple: [Uvea Island, hasTraditionalMonarchy, yes]
-
A.
traditionalMonarchy
chosen
Indicates a system where a monarchy operates according to long-established customs, hereditary succession, and historical institutions rather than modern or codified reforms.
-
B.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
C.
hasCentralizedMonarchy
Indicates that a political entity is governed by a single monarch who holds primary, centralized authority over the state.
-
D.
hasMonarchicalOrder
Indicates that there exists a hierarchical structure of authority organized according to monarchical principles (e.g., ranks, succession, or rule by a monarch).
-
E.
hasTraditionalRulers
Indicates that one entity possesses or is governed by traditional rulers associated with it.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: May 3, 2026, 4:31 p.m.