Triple
T34823091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kootenai |
E1003840
|
entity |
| Predicate | environmentAssociation |
P17695
|
FINISHED |
| Object | rivers |
—
|
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: rivers | Statement: [Kootenai, environmentAssociation, rivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentAssociation Context triple: [Kootenai, environmentAssociation, rivers]
-
A.
environmentalFeatureOf
Indicates a relationship where one entity is a natural or environmental characteristic, component, or attribute of another entity or place.
-
B.
environmentalConnection
chosen
Indicates a relationship where one entity affects, is affected by, or is contextually linked to another through environmental factors, conditions, or impacts.
-
C.
environmentRole
Indicates the functional role or influence that one entity has within or upon a particular environment or environmental context.
-
D.
habitatOfNotableSpecies
Indicates that a location serves as the natural environment or living area for one or more notable species.
-
E.
associatedWithWildlifeArea
Indicates that an entity has a connection, involvement, or linkage with a designated wildlife area.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77adf71d88190812e930bcf1e2ce5 |
completed | May 3, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 4 p.m.