Triple
T10214236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Core Animation |
E242401
|
entity |
| Predicate | supportsOpacity |
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: [Core Animation, supportsOpacity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOpacity Context triple: [Core Animation, supportsOpacity, true]
-
A.
hasTransparencyRequirement
Indicates that one entity is obligated to provide clear, accessible information or disclosure to another entity or to the public.
-
B.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
C.
supportsOverscan
Indicates that a display device or system is capable of handling overscan, meaning it can properly show content that extends beyond the nominal visible screen area.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
isTransparentTo
Indicates that one entity allows another entity (such as light, information, or influence) to pass through or be perceived without obstruction or concealment.
- 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.