Triple
T20165509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES Four Score |
E491815
|
entity |
| Predicate | hasSwitch |
P34291
|
FINISHED |
| Object | player 1/2 select switch |
—
|
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: player 1/2 select switch | Statement: [NES Four Score, hasSwitch, player 1/2 select switch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSwitch Context triple: [NES Four Score, hasSwitch, player 1/2 select switch]
-
A.
hasOnboardSwitch
chosen
Indicates that one entity is equipped with a built-in switch located on or within it.
-
B.
hasSwitchPalace
Indicates that a level or area contains or is associated with a Switch Palace.
-
C.
hasSwitchbacks
Indicates that a path, road, or trail includes sharp, back-and-forth turns (zigzags) used to navigate steep terrain.
-
D.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
E.
switchOnBy
Indicates that an entity is turned on or activated as the result of an action performed 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.