Triple
T26302764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedonkohe band |
E661602
|
entity |
| Predicate | originalBandOf |
P25537
|
FINISHED |
| Object | Geronimo |
—
|
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: Geronimo | Statement: [Bedonkohe band, originalBandOf, Geronimo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBandOf Context triple: [Bedonkohe band, originalBandOf, Geronimo]
-
A.
producerBand
Indicates that one band serves as the producer (overseeing or managing the creation and recording) of another band’s music or releases.
-
B.
hasOriginBand
Indicates that an entity (such as a musician or musical act) is or was originally a member of a specified band.
-
C.
originalBandMember
Indicates that a person was part of the band’s lineup at the time the band was first formed.
-
D.
originatedFromBand
chosen
Indicates that an entity (such as a musician or group) originally came from or was formed as part of a particular band.
-
E.
associatedBandOrigin
Indicates that there is a relationship between a musical band and the geographic place from which that band originates or is closely associated.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 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 26, 2026, 10:16 p.m.