Triple
T140365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois militia |
E2836
|
entity |
| Predicate | serviceObligation |
P445
|
FINISHED |
| Object | short-term enlistments |
—
|
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: short-term enlistments | Statement: [Illinois militia, serviceObligation, short-term enlistments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceObligation Context triple: [Illinois militia, serviceObligation, short-term enlistments]
-
A.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
B.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
obligationInArticleI
Indicates that a specified obligation is established, defined, or governed within Article I of a legal or constitutional document.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257c679d88190bc71775dab2cfc64 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.