Triple
T4727190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Cadet Force |
E104912
|
entity |
| Predicate | typicalJoiningAge |
P14567
|
FINISHED |
| Object | around 12 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: around 12 years | Statement: [Combined Cadet Force, typicalJoiningAge, around 12 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalJoiningAge Context triple: [Combined Cadet Force, typicalJoiningAge, around 12 years]
-
A.
ageAtMarriage
Indicates the age a person was when they got married.
-
B.
typicalLeavingAge
Indicates the age at which entities (such as people or groups) usually or most commonly leave a given context, place, or situation.
-
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.
typicalAgeAtSelection
Indicates the usual or most common age at which an entity is chosen or selected for a particular role, status, or process.
-
E.
typicalAgeOfVoters
Indicates the usual or most common age range of individuals who participate as voters in elections or voting processes.
- 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.