Triple
T15326448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Buffalo Creek |
E366423
|
entity |
| Predicate | locationOfSigning |
P441
|
FINISHED |
| Object | Buffalo 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: Buffalo Creek | Statement: [Treaty of Buffalo Creek, locationOfSigning, Buffalo Creek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buffalo Creek Context triple: [Treaty of Buffalo Creek, locationOfSigning, Buffalo Creek]
-
A.
Buffalo Creek
chosen
Buffalo Creek is a waterway whose name inspired that of the city of Buffalo in New York.
-
B.
Onion Creek
Onion Creek is a stream in Central Texas known for flowing through the Austin area and contributing to local parks, greenbelts, and floodplains.
-
C.
Well Creek
Well Creek is a waterway associated with the locality of Upwell in England, forming part of the region’s drainage and navigation network.
-
D.
Buck Creek
Buck Creek is a stream in central Alabama known for flowing through the city of Helena and serving as a local natural and recreational feature.
-
E.
Buck Creek
Buck Creek is a mountain stream in Washington State that flows through the North Cascades before joining the Suiattle River.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dfd8f048190831b463a2728eafe |
completed | April 16, 2026, 1:40 a.m. |
Created at: April 10, 2026, 3:16 a.m.