Triple
T1259998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bread and Roses Strike |
E12475
|
entity |
| Predicate | mottoInterpretation |
P26346
|
FINISHED |
| Object | demand for both material well-being and quality of life |
—
|
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: demand for both material well-being and quality of life | Statement: [Bread and Roses Strike, mottoInterpretation, demand for both material well-being and quality of life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoInterpretation Context triple: [Bread and Roses Strike, mottoInterpretation, demand for both material well-being and quality of life]
-
A.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
B.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
C.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
D.
mottoOriginal
Indicates that one entity is the original wording or form of another entity’s motto.
-
E.
translationOfMotto
Indicates that one motto is a translation of another motto in a different language.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc503e88190b237210a61228dd8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd98b62c8190a5f6710345c0537d |
completed | March 1, 2026, 10:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.