Triple
T32066308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's Tough to be a Bug! |
E818891
|
entity |
| Predicate | statusAtDisney'sAnimalKingdom |
P197207
|
FINISHED |
| Object | operating |
—
|
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: operating | Statement: [It's Tough to be a Bug!, statusAtDisney'sAnimalKingdom, operating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAtDisney'sAnimalKingdom Context triple: [It's Tough to be a Bug!, statusAtDisney'sAnimalKingdom, operating]
-
A.
hasSeaWorldFeature
Indicates that something possesses or includes a characteristic, attraction, or element specifically associated with SeaWorld.
-
B.
locatedInThemeParkType
Indicates that an entity is situated within or belongs to a specific type or category of theme park.
-
C.
replacedAtMagicKingdomBy
Indicates that one entity at Magic Kingdom was succeeded or substituted by another entity in the same context or role.
-
D.
replacedAtEpcotBy
Indicates that one entity was succeeded or substituted by another entity specifically at Epcot.
-
E.
statusAtTokyoDisneyland
Indicates the condition or state of something specifically while it is at Tokyo Disneyland.
- F. None of above. chosen
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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: May 1, 2026, 12:22 a.m.