Triple
T9040849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapter and Verse |
E216621
|
entity |
| Predicate | containsEarlyBandRecordings |
P86042
|
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: [Chapter and Verse, containsEarlyBandRecordings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEarlyBandRecordings Context triple: [Chapter and Verse, containsEarlyBandRecordings, true]
-
A.
containsReRecordedSong
Indicates that one entity (typically an album, release, or collection) includes a song that has been recorded again in a new version compared to its original recording.
-
B.
laterRecordedIn
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
-
C.
containsPreviouslyUnreleasedMaterial
Indicates that the subject includes content that has not been made publicly available or released prior to this instance.
-
D.
includesSongsFromPreviousAlbums
Indicates that a musical release contains one or more songs that were already issued on earlier albums.
-
E.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
- F. None of above. chosen
Provenance (4 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b100a348190a59abd6e9b815c63 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:09 p.m.