Triple
T772634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic American Engineering Record |
E16313
|
entity |
| Predicate | documentationType |
P19006
|
FINISHED |
| Object | primary source material |
—
|
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: primary source material | Statement: [Historic American Engineering Record, documentationType, primary source material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationType Context triple: [Historic American Engineering Record, documentationType, primary source material]
-
A.
documentTypeProduced
Indicates that one entity produces, generates, or creates a document of a specified type.
-
B.
draftType
Indicates the specific category or kind of draft associated with an entity or document (e.g., initial, revised, or final draft).
-
C.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
D.
doctypeSyntax
Indicates that one entity specifies or conforms to the syntax rules of a document type declaration (DOCTYPE) used in markup languages.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- F. None of above. chosen
Provenance (4 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_69a4a72eda6c81908205ae5a1e05cc20 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5a35c68819082429755c046e9a7 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.