Triple
T29603382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork Silver Creek |
E754510
|
entity |
| Predicate | hasSourceLocatedIn |
P66733
|
FINISHED |
| Object | Cascade Range |
—
|
NE NERFINISHED |
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: Cascade Range | Statement: [South Fork Silver Creek, hasSourceLocatedIn, Cascade Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceLocatedIn Context triple: [South Fork Silver Creek, hasSourceLocatedIn, Cascade Range]
-
A.
hasSourcePosition
Indicates that something originates from, is located at, or is associated with a specific source position or starting point.
-
B.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
C.
sourceLocatedOn
chosen
Indicates that the source entity is physically situated on the surface or area of the target entity.
-
D.
hasProgramLocation
Indicates that a program, event, or activity takes place at or is associated with a specific location.
-
E.
hasOriginalLocation
Indicates that an entity was initially located or situated at a specified place or position before any change or movement occurred.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 6:23 p.m.