Triple
T25902345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laredo Port of Entry |
E652650
|
entity |
| Predicate | primaryUseOfWorldTradeBridge |
P192547
|
FINISHED |
| Object | commercial trucks |
—
|
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: commercial trucks | Statement: [Laredo Port of Entry, primaryUseOfWorldTradeBridge, commercial trucks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseOfWorldTradeBridge Context triple: [Laredo Port of Entry, primaryUseOfWorldTradeBridge, commercial trucks]
-
A.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
B.
hasNumberOfMainBridges
Indicates the quantity of primary or main bridges associated with a given entity.
-
C.
PelješacBridgePurpose
Indicates that the relationship specifies the intended function or primary purpose for which the Pelješac Bridge exists or was constructed.
-
D.
bridgeLiftUsedFor
Indicates that a bridge is raised or lifted to allow a particular purpose, such as the passage or use of something beneath or through it.
-
E.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: April 22, 2026, 8:26 a.m.