Triple
T13848485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Quest 2 |
E332870
|
entity |
| Predicate | weightApprox |
P1575
|
FINISHED |
| Object | 503 g |
—
|
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: 503 g | Statement: [Oculus Quest 2, weightApprox, 503 g]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightApprox Context triple: [Oculus Quest 2, weightApprox, 503 g]
-
A.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
B.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
C.
وزن
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
D.
weightSupport
Indicates that one entity bears or carries the physical weight of another, providing structural or mechanical support.
-
E.
weight
chosen
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b2a9788190b164760adec64ef6 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.