Triple
T32928600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pains and Penalties Bill 1820 |
E842337
|
entity |
| Predicate | targetedTitle |
P66896
|
FINISHED |
| Object | Queen Consort of the United Kingdom |
—
|
NE NERFINISHED |
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: Queen Consort of the United Kingdom | Statement: [Pains and Penalties Bill 1820, targetedTitle, Queen Consort of the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedTitle Context triple: [Pains and Penalties Bill 1820, targetedTitle, Queen Consort of the United Kingdom]
-
A.
aimedTitle
chosen
Indicates that one entity is the intended or targeted title or heading associated with another entity.
-
B.
providedTitle
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
C.
titleIIFocus
Indicates that the primary focus or subject of a Title II–related provision, requirement, or classification is the referenced entity.
-
D.
commonTitle
Indicates that two or more entities share the same title or designation.
-
E.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
- 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_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 1, 2026, 1:20 a.m.