Triple
T10604969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siobhan "Shiv" Roy |
E275848
|
entity |
| Predicate | politicalBackground |
P94882
|
FINISHED |
| Object | progressive politics |
—
|
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: progressive politics | Statement: [Siobhan "Shiv" Roy, politicalBackground, progressive politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalBackground Context triple: [Siobhan "Shiv" Roy, politicalBackground, progressive politics]
-
A.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
B.
politicalLegacyIncludes
Indicates that one entity’s political legacy encompasses, influences, or is carried forward by another entity.
-
C.
hasPoliticalFamily
Indicates that an entity is related by family ties to another entity involved in politics or holding political office.
-
D.
politicalLine
Indicates that one entity’s political views, ideology, or affiliation are aligned with or follow the same general stance as another entity.
-
E.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:32 p.m.