Triple
T26592108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicangu Lakota |
E667384
|
entity |
| Predicate | primaryModernLocation |
P8489
|
FINISHED |
| Object | Rosebud Indian Reservation |
—
|
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: Rosebud Indian Reservation | Statement: [Sicangu Lakota, primaryModernLocation, Rosebud Indian Reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryModernLocation Context triple: [Sicangu Lakota, primaryModernLocation, Rosebud Indian Reservation]
-
A.
modernizationLocation
Indicates the place or setting where a modernization process or upgrade occurs.
-
B.
uncertainModernLocation
Indicates that the present-day geographic location associated with an entity is not known with certainty or cannot be reliably determined.
-
C.
modernLocality
chosen
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
D.
modernLocationOfCity
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
-
E.
nearModernSite
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 27, 2026, 2:08 a.m.