Triple
T5223643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rialto Bridge |
E117930
|
entity |
| Predicate | hasCentralPortico |
P9740
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rialto Bridge, hasCentralPortico, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralPortico Context triple: [Rialto Bridge, hasCentralPortico, true]
-
A.
hasPortico
chosen
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
-
B.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
C.
hasFoyer
Indicates that an entity includes or is equipped with a foyer as part of its structure or layout.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
hasSeparateEntrances
Indicates that the related entities each have their own distinct entrance, rather than sharing a common one.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abd3ed48190bfd8d2f2ca399741 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.