Triple
T6292759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Colonial architecture |
E141057
|
entity |
| Predicate | hasTypicalOutdoorFeature |
P19771
|
FINISHED |
| Object | arcade |
—
|
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: arcade | Statement: [Spanish Colonial architecture, hasTypicalOutdoorFeature, arcade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalOutdoorFeature Context triple: [Spanish Colonial architecture, hasTypicalOutdoorFeature, arcade]
-
A.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
B.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
C.
exteriorFeature
chosen
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
D.
outdoorSection
Indicates that one entity is a section, area, or portion that is located outdoors or in an open-air environment relative to another entity.
-
E.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0642017588190b6c99c685653f6c2 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.