Triple
T20473648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Balance Board |
E502256
|
entity |
| Predicate | sensorsLocation |
P140226
|
FINISHED |
| Object | four corners of the board |
—
|
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: four corners of the board | Statement: [Wii Balance Board, sensorsLocation, four corners of the board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensorsLocation Context triple: [Wii Balance Board, sensorsLocation, four corners of the board]
-
A.
tracksSensor
Indicates that one entity continuously monitors and records data from a specified sensor.
-
B.
numberOfSensors
Indicates the quantity of sensors associated with or contained by a given entity.
-
C.
requiresExternalSensors
Indicates that performing this action or maintaining this relationship depends on input or data from sensors that are external to the entity itself.
-
D.
controlsLocation
Indicates that one entity has authority over, manages, or determines the status or use of a particular location.
-
E.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e699639eec81908f8bd24877b2b876 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:33 a.m.