Triple
T23225178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFCAT |
E580994
|
entity |
| Predicate | eligibilityAgeGroundDuty |
P14567
|
FINISHED |
| Object | typically 20 to 26 years |
—
|
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: typically 20 to 26 years | Statement: [AFCAT, eligibilityAgeGroundDuty, typically 20 to 26 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityAgeGroundDuty Context triple: [AFCAT, eligibilityAgeGroundDuty, typically 20 to 26 years]
-
A.
militaryAge
Indicates that an entity is within the age range typically considered eligible for military service.
-
B.
minimumAgeForCivilians
Indicates the lowest age at which civilian individuals are legally permitted or recognized for a specified right, activity, or status.
-
C.
typicalEligibilityAge
chosen
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
D.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
E.
canAgeFor
Indicates that one entity is capable of undergoing an aging or maturation process for the benefit, use, or context of another entity.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922d30b08190a3c54bab58f5c8e7 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.