Triple
T24868317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza del Castillo |
E622346
|
entity |
| Predicate | hasStreetLevelArcades |
P24796
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Plaza del Castillo, hasStreetLevelArcades, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetLevelArcades Context triple: [Plaza del Castillo, hasStreetLevelArcades, yes]
-
A.
hasArcades
chosen
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
-
B.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
C.
upperDeckLanes
Indicates that the related entities are lanes located on the upper deck level of a multi-level structure (such as a roadway, bridge, or parking facility).
-
D.
notableArcadeGame
Indicates that the subject is an arcade game that is particularly famous, influential, or otherwise noteworthy.
-
E.
hasStreetLifeCharacteristic
Indicates that an entity exhibits a particular quality, feature, or condition related to street life or street-level activity.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:23 a.m.