Triple
T29462970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coordinate |
E747292
|
entity |
| Predicate | hasListeningFormat |
P176273
|
FINISHED |
| Object | digital download |
—
|
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: digital download | Statement: [Coordinate, hasListeningFormat, digital download]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListeningFormat Context triple: [Coordinate, hasListeningFormat, digital download]
-
A.
hasListeningEvent
Indicates that an entity participates in or is associated with an event in which listening or audio consumption occurs.
-
B.
hasIntendedListeningMode
Indicates that an entity is associated with a specific listening configuration or mode that it is designed or intended to use.
-
C.
hasCurrentFormat
chosen
Indicates that an entity currently exists, is stored, or is represented in a particular format.
-
D.
hasListeningContext
Indicates that an entity is associated with a particular listening situation or environment in which audio is being received or monitored.
-
E.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 3:51 p.m.