Triple
T3537625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario 64 DS |
E74805
|
entity |
| Predicate | cameraControl |
P43677
|
FINISHED |
| Object | touch screen |
—
|
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: touch screen | Statement: [Super Mario 64 DS, cameraControl, touch screen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraControl Context triple: [Super Mario 64 DS, cameraControl, touch screen]
-
A.
cameraConfiguration
chosen
Indicates the specific setup or arrangement of a camera’s parameters or components in a given context.
-
B.
cameraStyle
Indicates the characteristic visual approach or technique used by a camera in capturing or presenting imagery.
-
C.
viewerInteraction
Indicates that one entity engages with or responds to content presented by another entity, such as by viewing, reacting, or otherwise interacting with it.
-
D.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
E.
mediaControl
Indicates a relationship where one entity directs, regulates, or influences the creation, distribution, or content of media controlled by another entity.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcc928248190b851f8280d58cfcf |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.