Triple
T21335976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix (amusement attraction) |
E526047
|
entity |
| Predicate | likelyIncludes |
P1393
|
FINISHED |
| Object | fire-themed visual effects |
—
|
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: fire-themed visual effects | Statement: [Phoenix (amusement attraction), likelyIncludes, fire-themed visual effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyIncludes Context triple: [Phoenix (amusement attraction), likelyIncludes, fire-themed visual effects]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
C.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
-
D.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e898d7d8b88190b2f346e4592b3bc5 |
completed | April 22, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:43 p.m.