Triple
T1127843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 145th Street Bridge |
E24759
|
entity |
| Predicate | allowsVesselPassage |
P13009
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [145th Street Bridge, allowsVesselPassage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsVesselPassage Context triple: [145th Street Bridge, allowsVesselPassage, yes]
-
A.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
B.
operatesVessel
Indicates that an agent is responsible for controlling, managing, or running the operation of a vessel.
-
C.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
D.
navigability
chosen
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
E.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.