Triple
T17214341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hobbit (1982 video game) |
E417812
|
entity |
| Predicate | hasVisuals |
P126424
|
FINISHED |
| Object | static illustrations |
—
|
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: static illustrations | Statement: [The Hobbit (1982 video game), hasVisuals, static illustrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisuals Context triple: [The Hobbit (1982 video game), hasVisuals, static illustrations]
-
A.
hasVisualIndicator
Indicates that an entity is associated with some form of visual cue or marker that signals its status, condition, or presence.
-
B.
hasVisualImpact
Indicates that one entity affects or influences the visual appearance or aesthetic perception of another.
-
C.
visuallyDefines
Indicates that one entity establishes or clarifies the appearance, form, or visual characteristics of another entity.
-
D.
hasVisualCharacter
Indicates that one entity possesses or exhibits a particular visual appearance, style, or graphical characteristic defined by another entity.
-
E.
hasAdvertisingVisual
Indicates that an entity includes, is associated with, or uses a specific visual element or asset for advertising purposes.
- F. None of above. chosen
Provenance (4 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc8d3e88190a89bee6b75392360 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.