Triple
T37665653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switch 2 |
E937813
|
entity |
| Predicate | hasDisplayDetails |
P200699
|
FINISHED |
| Object | unconfirmed (as of 2024) |
—
|
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: unconfirmed (as of 2024) | Statement: [Switch 2, hasDisplayDetails, unconfirmed (as of 2024)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplayDetails Context triple: [Switch 2, hasDisplayDetails, unconfirmed (as of 2024)]
-
A.
hasDisplayStructure
Indicates that an entity is associated with a particular arrangement or organization of visual elements used for display or presentation.
-
B.
hasDisplayBehavior
Indicates that an entity exhibits a particular way or pattern of presenting information or visuals.
-
C.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
D.
hasInternalDisplay
Indicates that an entity is equipped with a built-in display screen as part of its own hardware.
-
E.
hasDisplayArea
Indicates that an entity includes or is associated with a specific physical or virtual area used for displaying content or items.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
| PDg | Predicate description generation | batch_69ffa15c3f348190a59403bc72ac9ed4 |
completed | May 9, 2026, 9:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.