Triple
T8491099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Hawaii |
E200969
|
entity |
| Predicate | unificationCompleted |
P83007
|
FINISHED |
| Object | 1810 |
—
|
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: 1810 | Statement: [Kingdom of Hawaii, unificationCompleted, 1810]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationCompleted Context triple: [Kingdom of Hawaii, unificationCompleted, 1810]
-
A.
unificationType
Indicates the specific manner or category in which two or more entities are combined, merged, or treated as a single unified whole.
-
B.
unificationPossible
Indicates that two entities can be combined or reconciled into a single, consistent representation under a shared set of constraints or rules.
-
C.
unificationLedTo
Indicates that a process of unifying previously separate entities resulted in or caused a particular outcome or state.
-
D.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55af3f48190a8cd64cdce0ebd4c |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.