Triple
T27969087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Leota |
E704805
|
entity |
| Predicate | locationInAttraction |
P80061
|
FINISHED |
| Object | exit crypt |
—
|
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: exit crypt | Statement: [Little Leota, locationInAttraction, exit crypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInAttraction Context triple: [Little Leota, locationInAttraction, exit crypt]
-
A.
locatedInAttractionScene
chosen
Indicates that one entity is situated within or is part of the setting or scene of an attraction.
-
B.
attractionLocatedIn
Indicates that an attraction (such as a landmark, site, or point of interest) is geographically situated within a specified location or area.
-
C.
isPartOfAttraction
Indicates that something is a component or sub-element within a larger attraction or point of interest.
-
D.
locatedInThemeParkType
Indicates that an entity is situated within or belongs to a specific type or category of theme park.
-
E.
containsAttraction
Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: April 27, 2026, 7:36 p.m.