Triple
T6440652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother (After the Fall) |
E138211
|
entity |
| Predicate | appearsOnPlatforms |
P39167
|
FINISHED |
| Object | VR platforms |
—
|
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 platforms | Statement: [Mother (After the Fall), appearsOnPlatforms, VR platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnPlatforms Context triple: [Mother (After the Fall), appearsOnPlatforms, VR platforms]
-
A.
platformsDevelopedFor
chosen
Indicates the platforms (e.g., operating systems, devices, or environments) for which something has been specifically created or adapted.
-
B.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
C.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
D.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
E.
typicalPlatform
Indicates that something commonly or usually serves as the platform or environment on which another thing operates, appears, or is based.
- 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.