Triple
T1550704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kill Van Kull |
E33082
|
entity |
| Predicate | bayonneBridgeCarries |
P31147
|
FINISHED |
| Object | vehicular traffic |
—
|
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: vehicular traffic | Statement: [Kill Van Kull, bayonneBridgeCarries, vehicular traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bayonneBridgeCarries Context triple: [Kill Van Kull, bayonneBridgeCarries, vehicular traffic]
-
A.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
B.
inBayBridgeSystem
Indicates that an entity is located within or forms part of the Bay Bridge system.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
E.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69aa573ee8e0819084abf59f1ddbd1da |
completed | March 6, 2026, 4:25 a.m. |
Created at: March 4, 2026, 7:26 p.m.