Triple
T35214479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolan Boogie |
E1016782
|
entity |
| Predicate | bandCountryOfOrigin |
P26
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Bolan Boogie, bandCountryOfOrigin, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandCountryOfOrigin Context triple: [Bolan Boogie, bandCountryOfOrigin, United Kingdom]
-
A.
laterCountryOfOrigin
Indicates that an entity’s country of origin changed, and this predicate specifies the country that became its origin at a later time than a previously associated country.
-
B.
leaderCountryOfOrigin
Indicates the country from which a leader originates or holds primary national affiliation.
-
C.
originCountryStyle
Indicates that something is characterized by or created in the style or manner typical of a particular country of origin.
-
D.
formationCountry
Indicates the country in which an entity (such as an organization, company, or group) was originally formed or established.
-
E.
countryOfOrigin
chosen
Indicates the country from which an entity originally comes or was first produced, created, or established.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.