Triple
T29978588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVPlayerItem |
E761518
|
entity |
| Predicate | observableVia |
P20811
|
FINISHED |
| Object | Key-value observing |
—
|
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: Key-value observing | Statement: [AVPlayerItem, observableVia, Key-value observing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observableVia Context triple: [AVPlayerItem, observableVia, Key-value observing]
-
A.
observableWith
chosen
Indicates that one entity can be detected, measured, or perceived through the use of another specified entity or method.
-
B.
observableFrom
Indicates that one entity can be perceived, detected, or measured from the vantage point or context of another entity.
-
C.
observableType
Indicates that one entity is classified as a specific kind or category of observable phenomenon or measurable event associated with another entity.
-
D.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
E.
observedWith
Indicates that two or more entities are seen, detected, or recorded together in the same context, event, or observation.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 6:34 p.m.