Triple
T4318888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Record Commission |
E96460
|
entity |
| Predicate | archivesConcerned |
P53210
|
FINISHED |
| Object | Chancery records |
—
|
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: Chancery records | Statement: [Record Commission, archivesConcerned, Chancery records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesConcerned Context triple: [Record Commission, archivesConcerned, Chancery records]
-
A.
archivalConcern
Indicates a relationship where something is regarded as important or relevant for preservation, documentation, or long-term archival purposes.
-
B.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
-
C.
archivesScope
chosen
Indicates that one entity defines or delimits the scope or coverage of another entity’s archival content or records.
-
D.
archivesModel
Indicates that one entity stores and preserves another entity as an archived model for long-term reference or retrieval.
-
E.
archivesHeldIn
Indicates that archival materials or records are stored, maintained, or preserved at a specified location or institution.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.