Triple
T149312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hansard |
E3396
|
entity |
| Predicate | archive |
P3262
|
FINISHED |
| Object | historical debates of UK Parliament |
—
|
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: historical debates of UK Parliament | Statement: [Hansard, archive, historical debates of UK Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archive Context triple: [Hansard, archive, historical debates of UK Parliament]
-
A.
archivesType
chosen
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
-
B.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
C.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
draft
Indicates that one entity prepares an initial or preliminary version of something, typically a document, plan, or design, which may be revised later.
-
E.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.