Triple
T7165173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusoponte |
E167047
|
entity |
| Predicate | bridgeFunction |
P69631
|
FINISHED |
| Object | road 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: road traffic | Statement: [Lusoponte, bridgeFunction, road traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeFunction Context triple: [Lusoponte, bridgeFunction, road traffic]
-
A.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
B.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
C.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
D.
bridgeCarries
chosen
Indicates that a bridge serves as a route or support structure for transporting or conveying something (such as vehicles, pedestrians, or utilities) across an obstacle.
-
E.
bridgePosition
Indicates the spatial or structural position of a bridge relative to other referenced elements or locations.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e832d2548190aacff0de80dbc268 |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.