Triple
T877430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ap |
E18952
|
entity |
| Predicate | hasMainVoterBase |
P21010
|
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: [Ap, hasMainVoterBase, working class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainVoterBase Context triple: [Ap, hasMainVoterBase, working class]
-
A.
hasMainProponent
Indicates that one entity is the primary advocate, champion, or leading supporter of another entity.
-
B.
hasMainRepresentative
Indicates that one entity serves as the primary or official representative of another entity.
-
C.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
-
D.
hasMajorityIn
Indicates that one entity holds more than half of the control, ownership, or representation within another entity or group.
-
E.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb06ea88190962502172d434eb4 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.