Triple
T37470606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Draven |
E931141
|
entity |
| Predicate | hasVisual |
P99801
|
FINISHED |
| Object | red-skinned Venthyr with wings |
—
|
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: red-skinned Venthyr with wings | Statement: [General Draven, hasVisual, red-skinned Venthyr with wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisual Context triple: [General Draven, hasVisual, red-skinned Venthyr with wings]
-
A.
hasVisuals
Indicates that one entity includes, displays, or is associated with visual elements or imagery related to another entity.
-
B.
hasVisualCharacter
chosen
Indicates that one entity possesses or exhibits a particular visual appearance, style, or graphical characteristic defined by another entity.
-
C.
hasVisualIndicator
Indicates that an entity is associated with some form of visual cue or marker that signals its status, condition, or presence.
-
D.
hasVisualImpact
Indicates that one entity affects or influences the visual appearance or aesthetic perception of another.
-
E.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:17 p.m.