Triple
T25372753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Toad's Wild Ride |
E632970
|
entity |
| Predicate | hasFormerVersionAt |
P24987
|
FINISHED |
| Object | Magic Kingdom |
—
|
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: Magic Kingdom | Statement: [Mr. Toad's Wild Ride, hasFormerVersionAt, Magic Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerVersionAt Context triple: [Mr. Toad's Wild Ride, hasFormerVersionAt, Magic Kingdom]
-
A.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
B.
hasVersionIn
chosen
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
C.
hasFormerEntity
Indicates that one entity previously existed in a different form, role, or identity that is represented by another entity.
-
D.
hasEarlierVersionPerformedBy
Indicates that an earlier version of an action, process, or performance was carried out by a specified agent or performer.
-
E.
hasFirstVersion
Indicates that one entity is the earliest or original version in a sequence of versions related to another 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 1:38 p.m.