Triple
T28489850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Davis + 19-piece orchestra |
E720930
|
entity |
| Predicate | primaryLocationOfRecording |
P8088
|
FINISHED |
| Object | New York City |
—
|
NE NERFINISHED |
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: New York City | Statement: [Miles Davis + 19-piece orchestra, primaryLocationOfRecording, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationOfRecording Context triple: [Miles Davis + 19-piece orchestra, primaryLocationOfRecording, New York City]
-
A.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
B.
mediaLocation
Indicates the physical or digital place where a media item is stored, accessed, or made available.
-
C.
primaryRecordingSite
Indicates the main anatomical or spatial location where a recording or measurement was originally captured.
-
D.
widelyRecordedIn
Indicates that an event, fact, or phenomenon has been documented or captured in many different records, sources, or media.
-
E.
reportedLocation
Indicates that an entity has been specified or recorded as being at a particular location, typically based on a report or observation rather than direct verification.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: April 28, 2026, 3 a.m.