Triple
T36371962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean City, Washington |
E895783
|
entity |
| Predicate | distanceTo Ocean Shores, Washington (approximate miles) |
P64650
|
FINISHED |
| Object | about 5 miles |
—
|
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: about 5 miles | Statement: [Ocean City, Washington, distanceTo Ocean Shores, Washington (approximate miles), about 5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTo Ocean Shores, Washington (approximate miles) Context triple: [Ocean City, Washington, distanceTo Ocean Shores, Washington (approximate miles), about 5 miles]
-
A.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
B.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
C.
distanceToOlympia
Indicates the measured spatial distance between a given location or object and Olympia.
-
D.
distanceToOceanCity
chosen
Indicates the measured distance between a given location and Ocean City.
-
E.
distanceFromTacoma (miles)
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.