Triple
T6501080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USACC |
E148888
|
entity |
| Predicate | hasCadetPopulation |
P71153
|
FINISHED |
| Object | college students enrolled in Army ROTC |
—
|
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: college students enrolled in Army ROTC | Statement: [USACC, hasCadetPopulation, college students enrolled in Army ROTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadetPopulation Context triple: [USACC, hasCadetPopulation, college students enrolled in Army ROTC]
-
A.
hasCorpsOfCadets
Indicates that an institution maintains an organized corps of cadets as part of its structure or programs.
-
B.
hasCadetBranch
Indicates that one lineage, family, or house is a junior or offshoot branch derived from another main or senior line.
-
C.
admittedCadetsAged
Indicates that an institution has admitted cadets who are of a specified age or within a specified age range.
-
D.
hasCadetProgram
chosen
Indicates that an organization or entity offers or operates a cadet program for training or development.
-
E.
hasCadetType
Indicates that an entity is associated with or classified under a specific type or category of cadet.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:42 p.m.