Triple
T9151598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponte di Paderno |
E219597
|
entity |
| Predicate | hasRoadLevel |
P50259
|
FINISHED |
| Object | lower deck |
—
|
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: lower deck | Statement: [Ponte di Paderno, hasRoadLevel, lower deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadLevel Context triple: [Ponte di Paderno, hasRoadLevel, lower deck]
-
A.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
B.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
C.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
D.
hasStreetLevel
chosen
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
E.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96cf4548190a3a45172f0e9d0ec |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.