Triple
T11541401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandemonium! |
E273683
|
entity |
| Predicate | usesGraphicsType |
P28918
|
FINISHED |
| Object | polygonal graphics |
—
|
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: polygonal graphics | Statement: [Pandemonium!, usesGraphicsType, polygonal graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGraphicsType Context triple: [Pandemonium!, usesGraphicsType, polygonal graphics]
-
A.
graphicsType
chosen
Indicates the type or category of graphics associated with or used by an entity.
-
B.
usesGraphType
Indicates that one entity employs or is configured to operate with a specific type of graph representation or graph model.
-
C.
supportsGraphicalUserInterface
Indicates that an entity is capable of operating with or providing a graphical user interface for interaction.
-
D.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
-
E.
graphics
Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.