Triple
T7146368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moriori |
E166578
|
entity |
| Predicate | treatySettlementYear |
P75098
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Moriori, treatySettlementYear, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySettlementYear Context triple: [Moriori, treatySettlementYear, 2020]
-
A.
treatySignedYear
Indicates the calendar year in which a specific treaty was formally signed.
-
B.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
C.
treatyEnteredIntoForce
Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
-
D.
treatyPeriod
Indicates the span of time during which a treaty is in force or considered applicable.
-
E.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d3c48c8190a71a61a1d50cd7da |
completed | March 27, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.