Triple
T17186962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isis |
E417133
|
entity |
| Predicate | reasonForNameChangeInPromotion |
P2136
|
FINISHED |
| Object | association of acronym ISIS with extremist group |
—
|
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: association of acronym ISIS with extremist group | Statement: [Isis, reasonForNameChangeInPromotion, association of acronym ISIS with extremist group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNameChangeInPromotion Context triple: [Isis, reasonForNameChangeInPromotion, association of acronym ISIS with extremist group]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
C.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
D.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
E.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d96fc588190ad2177d8bb346373 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.