Triple
T29154524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonds–Kingston route |
E738999
|
entity |
| Predicate | municipalityAtEasternTerminus |
P88362
|
FINISHED |
| Object | City of Edmonds |
—
|
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: City of Edmonds | Statement: [Edmonds–Kingston route, municipalityAtEasternTerminus, City of Edmonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityAtEasternTerminus Context triple: [Edmonds–Kingston route, municipalityAtEasternTerminus, City of Edmonds]
-
A.
easternTerminusTown
chosen
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
-
B.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
C.
easternTerminusNearby
Indicates that the eastern endpoint of one entity is located close to the referenced entity.
-
D.
northernTerminusMunicipality
Indicates that a municipality serves as the northern endpoint or terminus of a route, line, or similar linear feature.
-
E.
easternTerminusRegion
Indicates the region in which something (such as a route, line, or path) has its eastern endpoint or terminus.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 11:44 a.m.