Triple
T8291870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McHenry Papers |
E193916
|
entity |
| Predicate | documentsActivity |
P82572
|
FINISHED |
| Object | service as U.S. Secretary of War |
—
|
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: service as U.S. Secretary of War | Statement: [McHenry Papers, documentsActivity, service as U.S. Secretary of War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsActivity Context triple: [McHenry Papers, documentsActivity, service as U.S. Secretary of War]
-
A.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
B.
documentList
Indicates a relationship where one entity serves as a list or collection of documents associated with another entity.
-
C.
documentsCommunity
Indicates that an entity records, describes, or provides information about a particular community.
-
D.
documentsPeriod
Indicates that one entity documents, records, or provides written evidence about a specific time period associated with another entity.
-
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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c9ccbfc81908825685c23b80d23 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.