Triple
T20500269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metroid Prime |
E503280
|
entity |
| Predicate | cameraSwitchesTo |
P140322
|
FINISHED |
| Object | third-person view for morph ball sections |
—
|
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: third-person view for morph ball sections | Statement: [Metroid Prime, cameraSwitchesTo, third-person view for morph ball sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraSwitchesTo Context triple: [Metroid Prime, cameraSwitchesTo, third-person view for morph ball sections]
-
A.
cameraSystem
Indicates a relationship where an entity functions as or is part of a camera-based monitoring or imaging system.
-
B.
mainCameraFlash
Indicates that the primary camera’s flash is used or activated during image capture.
-
C.
mainCameraSensor
Indicates that an entity functions as the primary camera sensor for another entity.
-
D.
toggleInCameraUI
Indicates that an entity is being switched between active and inactive states within a camera-related user interface.
-
E.
cameraConfiguration
Indicates the specific setup or arrangement of a camera’s parameters or components in a given context.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cc10cd08190915b6c29c6473f77 |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:35 a.m.