Triple
T25555810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xbox Guide button |
E640564
|
entity |
| Predicate | illuminationPurpose |
P159141
|
FINISHED |
| Object | indicating controller status |
—
|
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: indicating controller status | Statement: [Xbox Guide button, illuminationPurpose, indicating controller status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illuminationPurpose Context triple: [Xbox Guide button, illuminationPurpose, indicating controller status]
-
A.
illuminationPurpose
chosen
Indicates that one entity serves the purpose of providing light or illumination for another entity or context.
-
B.
illuminationCondition
Indicates the lighting or brightness conditions under which an event, observation, or interaction takes place.
-
C.
illuminationMedium
Indicates the medium or method through which illumination or light is produced or delivered in a given context.
-
D.
roleAtIllumination
Indicates that an entity holds or held a specific role or position at the organization Illumination.
-
E.
isIlluminatedBy
Indicates that one entity receives light from, or is lit up 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8ca2cf48190997cd68875571217 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 3:39 p.m.