Triple
T2800123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Democrat |
E53133
|
entity |
| Predicate | hasSocialPosition |
P43278
|
FINISHED |
| Object | support for civil rights |
—
|
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: support for civil rights | Statement: [New Democrat, hasSocialPosition, support for civil rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialPosition Context triple: [New Democrat, hasSocialPosition, support for civil rights]
-
A.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
B.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
C.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
D.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
-
E.
hasNotablePosition
Indicates that an entity holds or has held a position, role, or office considered notable or significant.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 9:58 p.m.