Triple
T6440702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mickey |
E138213
|
entity |
| Predicate | mediumFormat |
P51716
|
FINISHED |
| Object | VR game |
—
|
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: VR game | Statement: [Mickey, mediumFormat, VR game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumFormat Context triple: [Mickey, mediumFormat, VR game]
-
A.
mediumDisplayed
Indicates that a particular medium (such as an image, video, or document) is being shown or rendered in a given context or interface.
-
B.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
C.
mediumAppearance
Indicates that an entity appears in or is featured within a particular medium (such as a work, format, or communication channel).
-
D.
mediumCategory
chosen
Indicates the classification of an item or content according to the type or form of medium it belongs to (e.g., print, digital, audio, video).
-
E.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06968c6a88190a623da9bd3152a66 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.