Triple
T31902426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Station (Magic Kingdom) |
E814459
|
entity |
| Predicate | hasContained |
P126031
|
FINISHED |
| Object | guest exhibits |
—
|
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: guest exhibits | Statement: [Fire Station (Magic Kingdom), hasContained, guest exhibits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContained Context triple: [Fire Station (Magic Kingdom), hasContained, guest exhibits]
-
A.
hasContainment
Indicates that one entity spatially or logically encloses, includes, or holds another within its bounds.
-
B.
believedToContain
Indicates that something is thought or assumed to hold, include, or possess something else, without certainty.
-
C.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
-
D.
hasIncluded
chosen
Indicates that one entity has incorporated or contained another entity as part of itself or within its scope.
-
E.
previouslyContained
Indicates that one entity was contained within another entity at some point in the past, but is not necessarily contained there now.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: May 1, 2026, midnight