Triple
T29208685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1864 |
E740487
|
entity |
| Predicate | monarchDuringAdoption |
P168756
|
FINISHED |
| Object | Kamehameha V |
—
|
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: Kamehameha V | Statement: [Constitution of 1864, monarchDuringAdoption, Kamehameha V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchDuringAdoption Context triple: [Constitution of 1864, monarchDuringAdoption, Kamehameha V]
-
A.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
B.
monarchDesignate
Indicates that one entity is formally chosen or recognized as the future monarch of another entity or domain.
-
C.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
D.
monarchDuringBirth
Indicates that one entity was the reigning monarch at the time another entity was born.
-
E.
monarchInQuestion
Indicates that the referenced entity is the specific monarch being discussed or evaluated in the given context.
- F. None of above. chosen
Provenance (4 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 28, 2026, 12:10 p.m.