Triple
T20003635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WKInterfaceMap |
E494395
|
entity |
| Predicate | supportsZoom |
P203
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WKInterfaceMap, supportsZoom, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsZoom Context triple: [WKInterfaceMap, supportsZoom, true]
-
A.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
supportScale
Indicates that one entity enables or accommodates the other’s ability to grow or operate effectively at larger size, capacity, or load.
-
D.
supportsContentsScale
Indicates that an object can adjust its content rendering to match a specified display or screen scale factor.
-
E.
supportsScalingDirection
Indicates that one entity enables or is compatible with a particular direction or mode of scaling (such as scaling up, scaling down, or scaling out) of 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.