Triple
T4701600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Librarian’s Records Room |
E104284
|
entity |
| Predicate | hasMaterialForm |
P1845
|
FINISHED |
| Object | paper 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: paper records | Statement: [Librarian’s Records Room, hasMaterialForm, paper records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialForm Context triple: [Librarian’s Records Room, hasMaterialForm, paper records]
-
A.
hasMaterialType
chosen
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
B.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
-
C.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
D.
hadBusinessForm
Indicates that an entity possessed or utilized a particular business form or organizational structure in the context of its activities or operations.
-
E.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.