Triple
T2477861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selected Reserve |
E55130
|
entity |
| Predicate | timeCommitment |
P2796
|
FINISHED |
| Object | recurring drill periods and annual training |
—
|
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: recurring drill periods and annual training | Statement: [Selected Reserve, timeCommitment, recurring drill periods and annual training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeCommitment Context triple: [Selected Reserve, timeCommitment, recurring drill periods and annual training]
-
A.
commitmentTiming
chosen
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
B.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
C.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
D.
workLengthRequirement
Indicates that there is a specified minimum or exact duration of work required for something (e.g., a job, task, or role).
-
E.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.