Triple
T9824548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambridge–Aliquippa Bridge |
E238620
|
entity |
| Predicate | hasSpanOver |
P44555
|
FINISHED |
| Object | Ohio River navigation channel |
—
|
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: Ohio River navigation channel | Statement: [Ambridge–Aliquippa Bridge, hasSpanOver, Ohio River navigation channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpanOver Context triple: [Ambridge–Aliquippa Bridge, hasSpanOver, Ohio River navigation channel]
-
A.
isSpanning
chosen
Indicates that one entity extends across, covers, or bridges the full width, extent, or duration of another entity.
-
B.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
C.
hasMainSpanLength
Indicates the relationship specifying the primary or main span’s length associated with an entity.
-
D.
hasMovableSpan
Indicates that an object or structure includes a span or section that can be moved or repositioned rather than being fixed in place.
-
E.
leafSpan
Indicates the extent or range covered by a leaf, such as its length, width, or overall spread.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3181c688190afea3b27ee392a30 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.