Triple
T2520837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinnecock Indian Nation |
E55517
|
entity |
| Predicate | primaryLanguageToday |
P1252
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Shinnecock Indian Nation, primaryLanguageToday, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLanguageToday Context triple: [Shinnecock Indian Nation, primaryLanguageToday, English]
-
A.
primaryLanguageOf
chosen
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
B.
primaryLanguageConcerned
Indicates that the relationship or action specifically involves or pertains to the main or principal language in question.
-
C.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
D.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
E.
primaryLanguageSide1
Indicates that the specified language is the main or dominant language associated with the first participant or side in a relationship.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2367b6c819094239dfd12399643 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.