Triple
T3214867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archives and Mausolea Department |
E67367
|
entity |
| Predicate | usesArchiveType |
P3262
|
FINISHED |
| Object | imperial 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: imperial archives | Statement: [Archives and Mausolea Department, usesArchiveType, imperial archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArchiveType Context triple: [Archives and Mausolea Department, usesArchiveType, imperial archives]
-
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.
operatesArchive
Indicates that one entity manages and runs the archival functions or facilities of another entity.
-
C.
usesDirectory
Indicates that one entity makes use of or operates within a particular directory in a file system or organizational structure.
-
D.
archivesModel
Indicates that one entity stores and preserves another entity as an archived model for long-term reference or retrieval.
-
E.
usesRepository
Indicates that one entity relies on, accesses, or interacts with a particular repository as a resource or data source.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab085a408190af9fb40acca31a5f |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.