Triple
T13193675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vittorio Veneto |
E314054
|
entity |
| Predicate | hasSuperstructureType |
P73759
|
FINISHED |
| Object | tower bridge superstructure |
—
|
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: tower bridge superstructure | Statement: [Vittorio Veneto, hasSuperstructureType, tower bridge superstructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperstructureType Context triple: [Vittorio Veneto, hasSuperstructureType, tower bridge superstructure]
-
A.
superstructureType
chosen
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
-
B.
hasSuperstructurePosition
Indicates the relative location or placement of a component or element within the superstructure of an object or system.
-
C.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
D.
hasIslandSuperstructure
Indicates that one entity possesses or includes an island-like elevated central structure as a distinct component or feature.
-
E.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.