Triple
T32212482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMC 2 |
E822844
|
entity |
| Predicate | numberOfStereoViews |
P203483
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [TMC 2, numberOfStereoViews, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfStereoViews Context triple: [TMC 2, numberOfStereoViews, 3]
-
A.
stereoscopic3D
Indicates that the subject is presented or perceived using stereoscopic 3D techniques, creating a depth effect by delivering slightly different images to each eye.
-
B.
canAcquireStereoPairs
Indicates that an entity is capable of obtaining or generating stereo image pairs suitable for stereoscopic or depth-related processing.
-
C.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
-
D.
stereoConfiguration
Indicates how multiple audio channels are arranged and related to each other in a stereo sound setup.
-
E.
simultaneousViews
Indicates that two or more entities are being viewed or observed at the same time.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
| PDg | Predicate description generation | batch_6a018f9bd91c8190980967b4eef78a58 |
completed | May 11, 2026, 8:13 a.m. |
Created at: May 1, 2026, 12:37 a.m.