Triple
T20783128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21st Century Hits: Best of 2000–2012 |
E511551
|
entity |
| Predicate | hasLiveRecordings |
P104299
|
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: [21st Century Hits: Best of 2000–2012, hasLiveRecordings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveRecordings Context triple: [21st Century Hits: Best of 2000–2012, hasLiveRecordings, true]
-
A.
includesLiveRecordings
chosen
Indicates that the subject contains or features recordings captured from live performances rather than studio-produced versions.
-
B.
includesLiveRecordingFrom
Indicates that something contains or incorporates a live recording sourced from another entity.
-
C.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
D.
hasLivePerformancesRecorded
Indicates that live performances of an entity (such as a work, event, or artist) have been captured and stored as recordings.
-
E.
hasLiveVideoRelease
Indicates that an entity has an associated release of a live video recording.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28870e481909e7cbcdd6d4bc247 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.