Triple
T22911920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Been Away Too Long |
E568618
|
entity |
| Predicate | firstAirplay |
P19932
|
FINISHED |
| Object | 2012-09-27 |
—
|
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: 2012-09-27 | Statement: [Been Away Too Long, firstAirplay, 2012-09-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAirplay Context triple: [Been Away Too Long, firstAirplay, 2012-09-27]
-
A.
supportsAirPlay
Indicates that one entity is capable of sending or receiving media via Apple’s AirPlay streaming protocol in relation to another entity.
-
B.
hasNotableAirplay
chosen
Indicates that something (typically a song, program, or audio content) has received a significant amount of broadcast play on radio or similar media.
-
C.
AppleTV4KFirstReleaseDate
Indicates the calendar date on which the first-generation Apple TV 4K device was initially released.
-
D.
AppleTV4KSecondGenerationReleaseDate
Indicates the date on which the second generation of Apple TV 4K was officially released.
-
E.
firstDevices
Indicates that the related entities are devices that occur or are used first in a sequence, order, or process relative to other devices.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18075a0048190bd150e2badeeb7c2 |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.