Triple
T768710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hay copy |
E16231
|
entity |
| Predicate | hasDocumentType |
P16808
|
FINISHED |
| Object | autograph manuscript |
—
|
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: autograph manuscript | Statement: [Hay copy, hasDocumentType, autograph manuscript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentType Context triple: [Hay copy, hasDocumentType, autograph manuscript]
-
A.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
B.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
-
D.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
E.
hasNodeType
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.