Triple
T1962774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East India Company Military Seminary, Addiscombe |
E42623
|
entity |
| Predicate | cadetAgeRange |
P3527
|
FINISHED |
| Object | teenage boys |
—
|
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: teenage boys | Statement: [East India Company Military Seminary, Addiscombe, cadetAgeRange, teenage boys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cadetAgeRange Context triple: [East India Company Military Seminary, Addiscombe, cadetAgeRange, teenage boys]
-
A.
admittedCadetsAged
chosen
Indicates that an institution has admitted cadets who are of a specified age or within a specified age range.
-
B.
hasCadetRank
Indicates that an entity holds or is assigned a cadet-level rank within a hierarchical or military-style ranking system.
-
C.
ageAtEnlistment
Indicates the age a person was when they enlisted in a service, organization, or role.
-
D.
militaryAge
Indicates that an entity is within the age range typically considered eligible for military service.
-
E.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.