Triple
T4934569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bush |
E110780
|
entity |
| Predicate | reasonForAlternateName |
P2136
|
FINISHED |
| Object | Name conflict in Canada with another band named Bush |
—
|
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: Name conflict in Canada with another band named Bush | Statement: [Bush, reasonForAlternateName, Name conflict in Canada with another band named Bush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForAlternateName Context triple: [Bush, reasonForAlternateName, Name conflict in Canada with another band named Bush]
-
A.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
C.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
D.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
E.
hasAlternativeNameForSameCity
Indicates that one city name is an alternative or variant name referring to the same city as another name.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7066ed548190a76a9559f90e3869 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.