Triple
T25502104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanosh Reservation |
E639141
|
entity |
| Predicate | landBaseFor |
P158603
|
FINISHED |
| Object | Kanosh Band of Paiute Indians |
E613357
|
NE 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: Kanosh Band of Paiute Indians | Statement: [Kanosh Reservation, landBaseFor, Kanosh Band of Paiute Indians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landBaseFor Context triple: [Kanosh Reservation, landBaseFor, Kanosh Band of Paiute Indians]
-
A.
landBaseFor
chosen
Indicates that one location serves as the primary land-based support or operational base for another entity (such as a unit, activity, or facility).
-
B.
landVariant
Indicates that one landform, terrain type, or land-related entity is an alternative or variant form of another.
-
C.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
-
D.
landLegSystem
Indicates a relationship where a landing system is specifically designed for or associated with a leg-based support or landing mechanism.
-
E.
land
Indicates coming down from the air or a higher position to make contact with and settle on a surface.
- F. None of above.
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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f802b5f8819081583610e0c59421 |
completed | May 2, 2026, 1:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12296965088190a7ba80f211586754 |
completed | May 23, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:45 p.m.