Triple
T37190536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian National Congress session of 1942 |
E921438
|
entity |
| Predicate | sloganPopularised |
P6980
|
FINISHED |
| Object | Do or Die |
—
|
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: Do or Die | Statement: [Indian National Congress session of 1942, sloganPopularised, Do or Die]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganPopularised Context triple: [Indian National Congress session of 1942, sloganPopularised, Do or Die]
-
A.
sloganUsedBy
Indicates that a particular slogan is employed or adopted by a specific entity (such as a person, organization, or brand) in its communication or branding.
-
B.
sloganUsedIn
chosen
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
C.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
D.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
E.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.