Triple
T13848480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Quest 2 |
E332870
|
entity |
| Predicate | IPDAdjustmentType |
P31649
|
FINISHED |
| Object | three-position physical adjustment |
—
|
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: three-position physical adjustment | Statement: [Oculus Quest 2, IPDAdjustmentType, three-position physical adjustment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPDAdjustmentType Context triple: [Oculus Quest 2, IPDAdjustmentType, three-position physical adjustment]
-
A.
adjustmentType
chosen
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
B.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
C.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
D.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
E.
billAdaptation
Indicates that a bill or legislative proposal has been modified or adjusted, typically in response to feedback, new information, or changing conditions.
- 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.