Triple
T35181571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertram Cooper |
E1015863
|
entity |
| Predicate | hasViewOnGovernment |
P193329
|
FINISHED |
| Object | anti-regulation |
—
|
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: anti-regulation | Statement: [Bertram Cooper, hasViewOnGovernment, anti-regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnGovernment Context triple: [Bertram Cooper, hasViewOnGovernment, anti-regulation]
-
A.
positionOnGovernment
Indicates an entity’s stance, role, or status within a governmental structure or political office.
-
B.
formedGovernmentOn
Indicates that an entity established or assumed control of a government on a specific date or at a specific point in time.
-
C.
associatedWithGovernmentInstitution
Indicates a relationship where an entity is connected, linked, or formally related to a government institution in some capacity.
-
D.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
E.
includeGovernmentOf
Indicates that one entity contains, encompasses, or incorporates the government of another entity as part of its structure or scope.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: May 3, 2026, 4:02 p.m.