Triple
T23054017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navajo Nation Treaty of 1868 |
E574102
|
entity |
| Predicate | hasContinuingEffect |
P150797
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Navajo Nation Treaty of 1868, hasContinuingEffect, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContinuingEffect Context triple: [Navajo Nation Treaty of 1868, hasContinuingEffect, yes]
-
A.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
B.
hasContinuo
Indicates that a musical work, section, or passage includes a basso continuo part or accompaniment.
-
C.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
D.
hasSecondaryEffect
Indicates that an action, event, or primary effect produces an additional, indirect, or consequential effect beyond its main intended outcome.
-
E.
hasContinuation
Indicates that one entity serves as a continuation or subsequent part of another entity in a sequence or process.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867eaed0819095c7da6b06101b12 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.