Triple
T36961840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serious Sam VR: The Last Hope |
E914325
|
entity |
| Predicate | supportsPlayArea |
P205667
|
FINISHED |
| Object | standing |
—
|
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: standing | Statement: [Serious Sam VR: The Last Hope, supportsPlayArea, standing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayArea Context triple: [Serious Sam VR: The Last Hope, supportsPlayArea, standing]
-
A.
hasPlayAreaType
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
B.
usesPlayingArea
Indicates that one entity makes use of a particular playing area as the space in which an activity or event takes place.
-
C.
settingWithinPlay
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
-
D.
supportsStubAreas
Indicates that one entity provides compatibility or functionality for handling stub areas associated with another entity.
-
E.
hasSpectatorArea
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.