Triple
T3182347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmon Creek, Washington |
E66617
|
entity |
| Predicate | distanceToPortlandInMiles |
P15604
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Salmon Creek, Washington, distanceToPortlandInMiles, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPortlandInMiles Context triple: [Salmon Creek, Washington, distanceToPortlandInMiles, 10]
-
A.
distanceToPortland
chosen
Indicates the measured distance between a given location and the city of Portland.
-
B.
distanceToPortlandMaine
Indicates the physical distance between a given location and the city of Portland, Maine.
-
C.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
D.
distanceToSaintPaul
Indicates the measured spatial distance between a given entity and the location of Saint Paul.
-
E.
distanceToPhoenix
Indicates the measured or estimated distance between a given entity’s location and the city of Phoenix.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6bd07888190b680eace8290d821 |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.