Triple
T14232617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeren |
E352788
|
entity |
| Predicate | associatedWithSupporterIdentity |
P74897
|
FINISHED |
| Object | working-class roots |
—
|
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 roots | Statement: [Boeren, associatedWithSupporterIdentity, working-class roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSupporterIdentity Context triple: [Boeren, associatedWithSupporterIdentity, working-class roots]
-
A.
associatedWithSupporters
chosen
Indicates that an entity has a relationship or connection with individuals or groups who support or advocate for it.
-
B.
supporterIdentity
Indicates that one entity is identified as a supporter (e.g., backer, advocate, or sponsor) of another entity or cause.
-
C.
associatedWithTeamIdentity
Indicates that an entity has a connection or relevance to the identity, branding, or defining characteristics of a particular team.
-
D.
sponsorAssociatedWith
Indicates a relationship where a sponsor is connected to, involved with, or responsible for supporting another entity.
-
E.
associatedWithProvider
Indicates that one entity has a connection or relationship with a specific provider, such as being supplied, managed, or serviced by that provider.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622cdd6481908befa179a9675bb5 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.