Triple
T1884609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verrazzano-Narrows Bridge |
E39933
|
entity |
| Predicate | deckClearanceBelow |
P6814
|
FINISHED |
| Object | 69 m |
—
|
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: 69 m | Statement: [Verrazzano-Narrows Bridge, deckClearanceBelow, 69 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckClearanceBelow Context triple: [Verrazzano-Narrows Bridge, deckClearanceBelow, 69 m]
-
A.
clearanceBelow
chosen
Indicates that one entity is positioned at a lower vertical clearance level than another, typically with less space between it and an underlying reference surface.
-
B.
hasClearanceBelow
Indicates that one entity’s clearance level is lower than another entity’s clearance level.
-
C.
clearanceBelowWhenRaised
Indicates that when one object is raised, there is a specified amount of vertical space (clearance) remaining below it relative to another object or reference surface.
-
D.
navigationClearanceType
Indicates the specific type or category of clearance granted for a navigation-related operation or movement.
-
E.
hasNavigationClearance
Indicates that an entity has been granted authorization to navigate through a specified area or along a particular route.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.