Triple
T33405454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic Skyway |
E855425
|
entity |
| Predicate | notRelocatedAsWholeTo |
P62852
|
FINISHED |
| Object | Disneyland |
—
|
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: Disneyland | Statement: [Magic Skyway, notRelocatedAsWholeTo, Disneyland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notRelocatedAsWholeTo Context triple: [Magic Skyway, notRelocatedAsWholeTo, Disneyland]
-
A.
partiallyRelocated
chosen
Indicates that an entity has been moved from its original location to a new one, but the relocation is incomplete or only affects part of the entity or its components.
-
B.
hasRelocation
Indicates that one entity is moved, transferred, or reassigned from one location or context to another.
-
C.
relocationResultedIn
Indicates that one relocation event caused or led to a particular outcome, state, or consequence.
-
D.
usedAsRelocationSiteDuring
Indicates that one entity served as a relocation site for another entity during a specified time or event.
-
E.
continuedAfterRelocation
Indicates that the same relationship or activity persisted without interruption after one of the involved entities changed location or was relocated.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.