Triple
T11620745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinnecock language |
E275628
|
entity |
| Predicate | historicalDocumentationBy |
P55104
|
FINISHED |
| Object | early colonial-era observers |
—
|
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: early colonial-era observers | Statement: [Shinnecock language, historicalDocumentationBy, early colonial-era observers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDocumentationBy Context triple: [Shinnecock language, historicalDocumentationBy, early colonial-era observers]
-
A.
historicallyDocumentedBy
chosen
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
B.
historicalEvidence
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
C.
historicalDocumentationLevel
Indicates the extent or quality of recorded evidence or documentation available about a particular event, entity, or relationship.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1206f1c81908d92024ef71958c0 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.