Triple
T23422416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squaxin Island people |
E560695
|
entity |
| Predicate | significantResource |
P152223
|
FINISHED |
| Object | salmon |
—
|
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: salmon | Statement: [Squaxin Island people, significantResource, salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantResource Context triple: [Squaxin Island people, significantResource, salmon]
-
A.
significantPort
Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
-
B.
significantScale
Indicates that the scale, size, or magnitude of something is notably large or important relative to a given context or standard.
-
C.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
D.
significantAfter
Indicates that one event or state occurs after another in a way that is temporally meaningful or non-trivially later, not just immediately or insignificantly afterward.
-
E.
significantProduct
Indicates that one entity is an especially important, impactful, or noteworthy product of another entity or process.
- F. None of above. chosen
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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a546c08c8190b57d90e88034eef3 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:46 p.m.