Triple
T31445973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chick-A-Pin Hill |
E802187
|
entity |
| Predicate | thematicSettingFor |
P25955
|
FINISHED |
| Object | Splash Mountain |
—
|
NE NERFINISHED |
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: Splash Mountain | Statement: [Chick-A-Pin Hill, thematicSettingFor, Splash Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicSettingFor Context triple: [Chick-A-Pin Hill, thematicSettingFor, Splash Mountain]
-
A.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
themedAs
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
-
C.
thematicTreatment
Indicates that one entity serves as the thematic focus, subject, or central topic treated, addressed, or explored by another entity.
-
D.
thematicFunction
Indicates how an entity participates in or contributes to the role structure of an event or situation (e.g., as agent, patient, instrument, etc.).
-
E.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:09 p.m.