Triple
T31954899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prerogative Court of Canterbury |
E815876
|
entity |
| Predicate | recordsHeldBy |
P39745
|
FINISHED |
| Object | The National Archives (Kew) |
—
|
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: The National Archives (Kew) | Statement: [Prerogative Court of Canterbury, recordsHeldBy, The National Archives (Kew)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsHeldBy Context triple: [Prerogative Court of Canterbury, recordsHeldBy, The National Archives (Kew)]
-
A.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
B.
recordHeldFor
Indicates that one entity is being kept, stored, or maintained on behalf of or in relation to another entity.
-
C.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
D.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
E.
archivesHeldBy
chosen
Indicates that archival materials or records are kept, managed, or preserved by a particular 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 12:08 a.m.