Triple
T31630474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otoe people |
E807148
|
entity |
| Predicate | treatyEvent |
P53913
|
FINISHED |
| Object | Treaty of 1830 |
—
|
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: Treaty of 1830 | Statement: [Otoe people, treatyEvent, Treaty of 1830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyEvent Context triple: [Otoe people, treatyEvent, Treaty of 1830]
-
A.
treatyOf
chosen
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
B.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
C.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
D.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
-
E.
treatyMention
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 30, 2026, 10:45 p.m.