Triple
T32028385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Twain (audio-animatronic) |
E817880
|
entity |
| Predicate | associatedParkSection |
P5641
|
FINISHED |
| Object | World Showcase |
E235330
|
NE 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 | Statement: [Mark Twain (audio-animatronic), associatedParkSection, World Showcase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedParkSection Context triple: [Mark Twain (audio-animatronic), associatedParkSection, World Showcase]
-
A.
locatedInParkSectionGroup
Indicates that something is situated within a specific section group of a park.
-
B.
associatedWithPark
Indicates a relationship in which an entity is connected or linked in some relevant way to a particular park.
-
C.
parkSection
chosen
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
-
D.
inPark
Indicates that one entity is located within or inside the boundaries of a park.
-
E.
hasParkSection
Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
- F. None of above.
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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ed4eff9188190a3c20a7b491b743d |
completed | June 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:17 a.m.