Triple
T21927722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 82nd Illinois Infantry Regiment |
E541484
|
entity |
| Predicate | musteredIntoServiceOn |
P61763
|
FINISHED |
| Object | 1862-10-23 |
—
|
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: 1862-10-23 | Statement: [82nd Illinois Infantry Regiment, musteredIntoServiceOn, 1862-10-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musteredIntoServiceOn Context triple: [82nd Illinois Infantry Regiment, musteredIntoServiceOn, 1862-10-23]
-
A.
musteredIntoService
Indicates that an entity has been formally enrolled or assembled into active duty or official service under an authority.
-
B.
musteredIn
chosen
Indicates that an individual or unit was formally enrolled, assembled, or brought into active service within an organization, typically a military force.
-
C.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
D.
ageAtEnlistment
Indicates the age a person was when they enlisted in a service, organization, or role.
-
E.
enlistmentYear
Indicates the year in which an entity formally joined or was enrolled into a service, organization, or group.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fc188481909c74fd5f1bd52258 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:46 p.m.