Triple
T25520662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts 1st Heavy Artillery Regiment |
E639636
|
entity |
| Predicate | laterDuty |
P170604
|
FINISHED |
| Object | field operations with the Army of the Potomac |
—
|
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: field operations with the Army of the Potomac | Statement: [Massachusetts 1st Heavy Artillery Regiment, laterDuty, field operations with the Army of the Potomac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDuty Context triple: [Massachusetts 1st Heavy Artillery Regiment, laterDuty, field operations with the Army of the Potomac]
-
A.
laterWork
Indicates that one work was created, published, or produced after another work in time.
-
B.
laterTask
Indicates that one task occurs after another in time, representing a temporal ordering where the first task precedes the laterTask.
-
C.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
-
D.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
E.
laterOffice
Indicates that one office or term of office occurs chronologically after another office or term.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 21, 2026, 3 p.m.