Triple

T15885574
Position Surface form Disambiguated ID Type / Status
Subject Stillwater, Oklahoma E385184 entity
Predicate namedAfter P63 FINISHED
Object Stillwater Creek 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: Stillwater Creek | Statement: [Stillwater, Oklahoma, namedAfter, Stillwater Creek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stillwater Creek
Context triple: [Stillwater, Oklahoma, namedAfter, Stillwater Creek]
  • A. Stillwater Creek chosen
    Stillwater Creek is a stream in north-central Oklahoma that flows through Payne County and helps drain the area around the city of Stillwater.
  • B. Stillwater Creek
    Stillwater Creek is a small waterway located near Frewsburg in western New York State.
  • C. Still Creek
    Still Creek is a small stream in eastern Pennsylvania that serves as a right-bank tributary of the Little Schuylkill River.
  • D. Contrary Creek
    Contrary Creek is a small tributary stream in Virginia known for its historically mining-related acid drainage that discolors the water before it enters Lake Anna.
  • E. Short Creek
    Short Creek was the original name of a remote, predominantly fundamentalist Mormon settlement that later became the twin border towns of Hildale, Utah, and Colorado City, Arizona.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1561a68d8819099e60e2f1f0db07a completed April 16, 2026, 9:35 p.m.
Created at: April 10, 2026, 4:51 a.m.