Triple
T1145865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 皇室 |
E23562
|
entity |
| Predicate | recognizedAsOldestContinuingMonarchy |
P4866
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [皇室, recognizedAsOldestContinuingMonarchy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsOldestContinuingMonarchy Context triple: [皇室, recognizedAsOldestContinuingMonarchy, true]
-
A.
oldestContinuingHereditaryMonarchy
chosen
Indicates that the subject is the longest-standing hereditary monarchy that has continued without interruption compared to all others.
-
B.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
C.
confirmedMonarch
Indicates that an entity has been formally recognized and validated as the legitimate monarch, typically through an official confirmation process.
-
D.
governingMonarchyAtCreation
Indicates the monarchy that held governing authority over an entity at the time the entity was created.
-
E.
lastMonarchOf
Indicates that one entity is the final reigning monarch of another entity, such as a country, kingdom, or territory.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc6e8c2081909fb3534413b7aacb |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.