Triple
T36393303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severn River Bridge |
E896390
|
entity |
| Predicate | onCorridorTo |
P185429
|
FINISHED |
| Object | Ocean City, Maryland |
—
|
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: Ocean City, Maryland | Statement: [Severn River Bridge, onCorridorTo, Ocean City, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onCorridorTo Context triple: [Severn River Bridge, onCorridorTo, Ocean City, Maryland]
-
A.
onCorridorBetween
Indicates that one entity is located along the corridor that lies between two other reference entities or areas.
-
B.
focusesOnCorridor
Indicates that an action, attention, or process is directed specifically toward a corridor or passageway.
-
C.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
D.
followedCorridor
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
E.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
- F. None of above. chosen
Provenance (4 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.