Triple
T10214262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Core Animation |
E242401
|
entity |
| Predicate | supportsRetinaDisplays |
P74451
|
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: [Core Animation, supportsRetinaDisplays, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRetinaDisplays Context triple: [Core Animation, supportsRetinaDisplays, true]
-
A.
supportsDisplayResolution
chosen
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
B.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
-
C.
supportsWideColorGamut
Indicates that one entity provides or enables compatibility with a wide color gamut capability for another entity or context.
-
D.
supportsExternalDisplay
Indicates that an entity is capable of connecting to and functioning with an external display device.
-
E.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa273bdc8190bc4cf67a7923cebc |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:04 a.m.