Triple
T8255006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of New Echota |
E193049
|
entity |
| Predicate | rejectedByCherokeeNationalCouncil |
P438
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Treaty of New Echota, rejectedByCherokeeNationalCouncil, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectedByCherokeeNationalCouncil Context triple: [Treaty of New Echota, rejectedByCherokeeNationalCouncil, true]
-
A.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
B.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
C.
rejectedAward
Indicates that an entity refused to accept or declined an award that was offered or granted to it.
-
D.
rejectedPractice
Indicates that one party has refused to accept, endorse, or continue a particular practice, method, or behavior associated with another party.
-
E.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f9f680819088f1d56e0f98974f |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.