Triple
T29037975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania 36 |
E737916
|
entity |
| Predicate | featuredCinematicMatchType |
P198487
|
FINISHED |
| Object | Firefly Fun House match |
—
|
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: Firefly Fun House match | Statement: [WrestleMania 36, featuredCinematicMatchType, Firefly Fun House match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredCinematicMatchType Context triple: [WrestleMania 36, featuredCinematicMatchType, Firefly Fun House match]
-
A.
featuredCinematicMatch
chosen
Indicates that a particular cinematic work has been selected or highlighted as a featured match in a given context or collection.
-
B.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
C.
hasCinematicFeature
Indicates that something possesses a specific cinematic characteristic, quality, or element related to film or visual storytelling.
-
D.
cinematicForm
Indicates that something is expressed, structured, or realized through the techniques, conventions, or medium of cinema or film.
-
E.
featuredMove
Indicates that a particular move is highlighted or given special prominence among other moves.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: April 28, 2026, 10 a.m.