Triple
T33368812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemo & Friends SeaRider |
E854427
|
entity |
| Predicate | uses3DProjection |
P95107
|
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: [Nemo & Friends SeaRider, uses3DProjection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uses3DProjection Context triple: [Nemo & Friends SeaRider, uses3DProjection, yes]
-
A.
has3DProjectionSystem
chosen
Indicates that an entity is equipped with or includes a 3D projection system.
-
B.
usesProjectionMappingOn
Indicates that one entity applies projection mapping techniques onto another entity, typically by projecting images or video content onto its surface.
-
C.
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.
-
D.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
-
E.
has3DGraphics
Indicates that something includes or supports three-dimensional graphical representation or rendering.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:35 a.m.