Triple
T1207530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Volunteers |
E25922
|
entity |
| Predicate | typicalEnlistmentTerm |
P540
|
FINISHED |
| Object | for the duration of the 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: for the duration of the war | Statement: [United States Volunteers, typicalEnlistmentTerm, for the duration of the war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnlistmentTerm Context triple: [United States Volunteers, typicalEnlistmentTerm, for the duration of the war]
-
A.
ageAtEnlistment
Indicates the age a person was when they enlisted in a service, organization, or role.
-
B.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
C.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
D.
militaryAge
Indicates that an entity is within the age range typically considered eligible for military service.
-
E.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc483b481908e5bfef5d2f4fc5a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.