Triple
T25417747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 15 |
E636886
|
entity |
| Predicate | hasKeyCrossing |
P33204
|
FINISHED |
| Object | Story Bridge |
—
|
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: Story Bridge | Statement: [State Route 15, hasKeyCrossing, Story Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyCrossing Context triple: [State Route 15, hasKeyCrossing, Story Bridge]
-
A.
isKeyCrossingFor
chosen
Indicates that one entity serves as a primary or critical crossing point (such as a bridge, intersection, or passage) for another entity’s movement or connectivity.
-
B.
hasCrossingPoint
Indicates that two or more entities intersect or share at least one common point in space or along their paths.
-
C.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
D.
isCrossBetween
Indicates that one entity is a hybrid or intermediate form resulting from the combination or mixing of two other entities.
-
E.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 1:55 p.m.