Triple
T30716281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | new-democratic revolution |
E782030
|
entity |
| Predicate | unitesClass |
P35330
|
FINISHED |
| Object | working class |
—
|
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: working class | Statement: [new-democratic revolution, unitesClass, working class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitesClass Context triple: [new-democratic revolution, unitesClass, working class]
-
A.
unites
chosen
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
combiningClass
Indicates that one entity functions as a combining diacritic or mark that attaches to a base character, specifying how it combines in text rendering or encoding.
-
C.
unionClassification
Indicates that an entity is categorized or designated according to a specific labor union or union-related classification.
-
D.
unitedWithTitle
Indicates that an entity has been joined or merged with another entity under a shared or combined title.
-
E.
unificationType
Indicates the specific manner or category in which two or more entities are combined, merged, or treated as a single unified whole.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:35 p.m.