Triple
T2623468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SED |
E59061
|
entity |
| Predicate | claimedToRepresent |
P32091
|
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: [SED, claimedToRepresent, working class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedToRepresent Context triple: [SED, claimedToRepresent, working class]
-
A.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
B.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
C.
claimsToBe
chosen
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
E.
signedByRepresentativeOf
Indicates that an item (such as a document or agreement) has been signed on behalf of a party by that party’s authorized representative.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.