Triple
T20003613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WKInterfaceGroup |
E494394
|
entity |
| Predicate | canContain |
P1433
|
FINISHED |
| Object | WKInterfaceTable |
—
|
NE NERFINISHED |
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: WKInterfaceTable | Statement: [WKInterfaceGroup, canContain, WKInterfaceTable]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WKInterfaceTable Context triple: [WKInterfaceGroup, canContain, WKInterfaceTable]
-
A.
WKInterfaceTable
chosen
WKInterfaceTable is a WatchKit user interface class used to manage and display table-based layouts on Apple Watch apps.
-
B.
WKInterfaceObject
WKInterfaceObject is a fundamental WatchKit class that represents and manages user interface elements in Apple Watch apps.
-
C.
WKInterfaceMap
WKInterfaceMap is a WatchKit interface object that lets developers embed and control interactive map content within Apple Watch apps.
-
D.
WKInterfaceController
WKInterfaceController is the primary controller class in WatchKit used to manage the interface and behavior of Apple Watch app scenes.
-
E.
WKInterfaceGroup
WKInterfaceGroup is a WatchKit user interface container used to group and layout multiple interface objects together on an Apple Watch app screen.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
Created at: April 11, 2026, 3:33 p.m.