Triple
T5254411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 44th New York Infantry |
E118663
|
entity |
| Predicate | musteredIn |
P61763
|
FINISHED |
| Object | 1861-09-24 |
—
|
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: 1861-09-24 | Statement: [44th New York Infantry, musteredIn, 1861-09-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musteredIn Context triple: [44th New York Infantry, musteredIn, 1861-09-24]
-
A.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
B.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
-
C.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
D.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
E.
garrisonDuringFormation
Indicates that a military unit is stationed in a specific garrison location during its period of formation or initial organization.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ba1cca88190bebd516851b9bf7f |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd787975788190848ffbac87896efe |
completed | March 20, 2026, 4:40 p.m. |
Created at: March 20, 2026, 1:50 p.m.