Triple
T9492357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alhóndiga de Granaditas |
E228920
|
entity |
| Predicate | visitorAccessibility |
P88924
|
FINISHED |
| Object | open to the public |
—
|
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: open to the public | Statement: [Alhóndiga de Granaditas, visitorAccessibility, open to the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorAccessibility Context triple: [Alhóndiga de Granaditas, visitorAccessibility, open to the public]
-
A.
visitorAccessPoint
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
D.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
E.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
- F. None of above. chosen
Provenance (4 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80ca26bc819084add20027aea4a5 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.