Triple
T32928628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pains and Penalties Bill 1820 |
E842337
|
entity |
| Predicate | evidenceGatheredBy |
P9384
|
FINISHED |
| Object | British agents on the Continent |
—
|
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: British agents on the Continent | Statement: [Pains and Penalties Bill 1820, evidenceGatheredBy, British agents on the Continent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceGatheredBy Context triple: [Pains and Penalties Bill 1820, evidenceGatheredBy, British agents on the Continent]
-
A.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
B.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
hasProcessEvidence
Indicates that there is supporting evidence for a process or procedure associated with the subject in relation to the object.
-
D.
collectedThrough
chosen
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
E.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0dbd5108190a3f47d397a2b3f63 |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.