Triple
T34117322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaycee, Wyoming |
E875008
|
entity |
| Predicate | hasNearbyCreek |
P8567
|
FINISHED |
| Object | Middle Fork Powder River |
—
|
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: Middle Fork Powder River | Statement: [Kaycee, Wyoming, hasNearbyCreek, Middle Fork Powder River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCreek Context triple: [Kaycee, Wyoming, hasNearbyCreek, Middle Fork Powder River]
-
A.
hasNearbyLake
Indicates that one entity is located close to or in the vicinity of a lake.
-
B.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
C.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
D.
riverTypeNearby
Indicates that one entity is located near a river of a specified type or classification.
-
E.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:53 a.m.