Triple
T9616561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de los Amigos |
E232232
|
entity |
| Predicate | locatedInParkSection |
P57709
|
FINISHED |
| Object | World Showcase Mexico Pavilion interior pyramid |
—
|
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: World Showcase Mexico Pavilion interior pyramid | Statement: [Plaza de los Amigos, locatedInParkSection, World Showcase Mexico Pavilion interior pyramid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInParkSection Context triple: [Plaza de los Amigos, locatedInParkSection, World Showcase Mexico Pavilion interior pyramid]
-
A.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
B.
isWithinPark
Indicates that one entity is located inside the boundaries of a park that contains it.
-
C.
locatedInAttractionScene
Indicates that one entity is situated within or is part of the setting or scene of an attraction.
-
D.
hasParkSection
chosen
Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
-
E.
openedInPark
Indicates that an entity was opened, inaugurated, or began operating within the boundaries of a park.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aad71a0819084ea00c2409e9922 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.