Triple
T38132399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactica |
E952258
|
entity |
| Predicate | hasVirtualRealityFeature |
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: [Galactica, hasVirtualRealityFeature, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirtualRealityFeature Context triple: [Galactica, hasVirtualRealityFeature, yes]
-
A.
virtualRealityOption
chosen
Indicates that an entity offers, supports, or is configured as a virtual reality mode, feature, or setting within a system or experience.
-
B.
virtualRealityProvider
Indicates that one entity serves as a provider or supplier of virtual reality services, systems, or experiences to another entity.
-
C.
hasOculus
Indicates that one entity possesses or is equipped with an oculus (a circular opening or eye-like feature).
-
D.
supportsPCVRConnection
Indicates that an entity enables or is compatible with establishing a PC-based virtual reality (VR) connection.
-
E.
hasVirtualExperience
Indicates that one entity possesses or has participated in a virtual or digitally simulated experience related to another entity.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:21 p.m.