Triple
T29570306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Apple Coaster |
E753284
|
entity |
| Predicate | virtualRealityOption |
P167454
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Big Apple Coaster, virtualRealityOption, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtualRealityOption Context triple: [Big Apple Coaster, virtualRealityOption, yes]
-
A.
virtualRealityVersionName
Indicates the name assigned to a specific version of a virtual reality experience, application, or environment.
-
B.
hasVirtualExperience
Indicates that one entity possesses or has participated in a virtual or digitally simulated experience related to another entity.
-
C.
virtualRealityRemoved
Indicates that a previously present virtual reality environment, experience, or component has been taken away, disabled, or no longer exists in the given context.
-
D.
viewOnReality
Indicates a subject’s overarching perspective, interpretation, or conceptual stance regarding the nature of reality.
-
E.
supportsPCVRConnection
Indicates that an entity enables or is compatible with establishing a PC-based virtual reality (VR) connection.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d46180881908ff6b2ce3a27b9c0 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 5:57 p.m.