Triple
T37788225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sports Champions |
E942013
|
entity |
| Predicate | supportsStereoscopic3D |
P84758
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sports Champions, supportsStereoscopic3D, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStereoscopic3D Context triple: [Sports Champions, supportsStereoscopic3D, true]
-
A.
stereoscopic3D
chosen
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.
has3DProjectionSystem
Indicates that an entity is equipped with or includes a 3D projection system.
-
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.
has3DGlasses
Indicates that an entity possesses or is equipped with 3D glasses.
-
E.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.