Triple
T8953985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | imperial chrysobulls |
E213425
|
entity |
| Predicate | archivesIn |
P10288
|
FINISHED |
| Object | monastic archives |
—
|
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: monastic archives | Statement: [imperial chrysobulls, archivesIn, monastic archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesIn Context triple: [imperial chrysobulls, archivesIn, monastic archives]
-
A.
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.
-
B.
archivesModel
Indicates that one entity stores and preserves another entity as an archived model for long-term reference or retrieval.
-
C.
archivesHeldIn
chosen
Indicates that archival materials or records are stored, maintained, or preserved at a specified location or institution.
-
D.
archivesFocus
Indicates that one entity preserves or stores another entity as a primary subject or area of concentration for future reference or use.
-
E.
archivesScope
Indicates that one entity defines or delimits the scope or coverage of another entity’s archival content or records.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6724f3e4819092c6b13d80871e80 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.