Triple
T28842263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell v Mirror Group Newspapers Ltd |
E728348
|
entity |
| Predicate | panel |
P165655
|
FINISHED |
| Object | Appellate Committee of the House of Lords |
—
|
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: Appellate Committee of the House of Lords | Statement: [Campbell v Mirror Group Newspapers Ltd, panel, Appellate Committee of the House of Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: panel Context triple: [Campbell v Mirror Group Newspapers Ltd, panel, Appellate Committee of the House of Lords]
-
A.
panels
Indicates that one entity is composed of, covered by, or divided into flat sections or segments formed by another entity.
-
B.
panelArea
Indicates the total surface area covered or occupied by a specific panel.
-
C.
panelDivision
Indicates a relationship where a larger panel or board is divided into smaller sections or segments.
-
D.
panelFound
Indicates that a specific panel has been located, identified, or successfully detected in a given context or environment.
-
E.
panelControl
Indicates a relationship where one entity controls, manages, or operates a panel associated with another entity.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6597388608190b0bcb812f4484f62 |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:41 a.m.