Triple
T26163837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UltrAslan |
E654188
|
entity |
| Predicate | fanStyle |
P160000
|
FINISHED |
| Object | use of pyrotechnics (where permitted) |
—
|
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: use of pyrotechnics (where permitted) | Statement: [UltrAslan, fanStyle, use of pyrotechnics (where permitted)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanStyle Context triple: [UltrAslan, fanStyle, use of pyrotechnics (where permitted)]
-
A.
fanStyle
chosen
Indicates the manner or style in which a fan (supporter or admirer) expresses their fandom toward a subject.
-
B.
fanType
Indicates the specific category or kind of fan associated with an entity, such as its design, purpose, or operating principle.
-
C.
fanPosition
Indicates the spatial placement or orientation of a fan relative to a reference point or object.
-
D.
fan
Indicates that one entity admires, supports, or is enthusiastically devoted to another entity, typically in a recreational or entertainment context.
-
E.
fangType
Indicates the specific kind or classification of fangs that an entity possesses.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c3d50208190ab0749009f70ffff |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:31 p.m.