Triple
T27910741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kane |
E705920
|
entity |
| Predicate | entranceEffect |
P114133
|
FINISHED |
| Object | ring-post fire blasts |
—
|
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: ring-post fire blasts | Statement: [Kane, entranceEffect, ring-post fire blasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceEffect Context triple: [Kane, entranceEffect, ring-post fire blasts]
-
A.
entranceGimmick
chosen
Indicates a distinctive feature, stunt, or presentation style used when someone or something makes an entrance.
-
B.
entranceTheme
Indicates the music or theme that plays when an entity makes their entrance or initial appearance.
-
C.
hasAutomaticEntrance
Indicates that an entity is equipped with an entrance that operates automatically (e.g., opens or closes without manual effort).
-
D.
entranceVisibility
Indicates how easily or clearly an entrance can be seen or recognized from a given viewpoint or approach.
-
E.
entranceDesigner
Indicates that an entity is responsible for designing the entrance of a building, structure, or space.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:49 p.m.