Triple

T2898026
Position Surface form Disambiguated ID Type / Status
Subject Indian reservations in the United States E63987 entity
Predicate historicallyResultedFrom P1823 FINISHED
Object treaties 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: treaties | Statement: [Indian reservations in the United States, historicallyResultedFrom, treaties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyResultedFrom
Context triple: [Indian reservations in the United States, historicallyResultedFrom, treaties]
  • A. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • B. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • C. historicallyBasedOn
    Indicates that something is derived from, inspired by, or modeled on historical events, sources, or precedents.
  • D. historicalOrigin chosen
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
  • E. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • 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_69ab4c45822c8190830c5f2bb97bcfd0 completed March 6, 2026, 9:51 p.m.
NER Named-entity recognition batch_69abe08fe3248190a6bb7de2a2c317b1 completed March 7, 2026, 8:23 a.m.
PD Predicate disambiguation batch_69abdd17bcdc8190aa47274a50ba4ad4 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:08 p.m.