Triple
T9140374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giralda |
E219309
|
entity |
| Predicate | allowsPublicAccess |
P30373
|
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: [Giralda, allowsPublicAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPublicAccess Context triple: [Giralda, allowsPublicAccess, yes]
-
A.
publicAccess
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
B.
isPubliclyAccessible
chosen
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
C.
hasPublicAccessRestrictions
Indicates that there are specific limitations or conditions governing public access to the associated resource or entity.
-
D.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
E.
requiresPublic
Indicates that an entity must be publicly accessible, visible, or usable in order for a related action, condition, or relationship to hold.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f2537881908956a9b0516e2d49 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.