Triple
T2520855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinnecock Indian Nation |
E55517
|
entity |
| Predicate | hasCasinoProject |
P14971
|
FINISHED |
| Object | Shinnecock gaming initiatives |
—
|
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: Shinnecock gaming initiatives | Statement: [Shinnecock Indian Nation, hasCasinoProject, Shinnecock gaming initiatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCasinoProject Context triple: [Shinnecock Indian Nation, hasCasinoProject, Shinnecock gaming initiatives]
-
A.
hasCasino
Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
-
B.
hasProject
chosen
Indicates that an entity is associated with or responsible for a particular project.
-
C.
hasNotableProject
Indicates that an entity is associated with a project that is distinguished or recognized as significant in some way.
-
D.
hasArcades
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
-
E.
hasCurrencyProject
Indicates that an entity is associated with or involved in a specific currency-related project.
- 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.