Triple
T38357722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Army training camp |
E1046379
|
entity |
| Predicate | typicalTraineeRank |
P7007
|
FINISHED |
| Object | Private |
—
|
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: Private | Statement: [United States Army training camp, typicalTraineeRank, Private]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTraineeRank Context triple: [United States Army training camp, typicalTraineeRank, Private]
-
A.
establishedRank
Indicates that a stable or officially recognized hierarchical position or level has been assigned to an entity relative to others.
-
B.
isEntryLevelRankFor
Indicates that a rank represents the lowest or starting level within a particular role, position, or hierarchy.
-
C.
typicalEnlistedGrade
Indicates the usual or standard military enlisted rank level associated with an entity.
-
D.
rankTypically
Indicates that one entity is usually or commonly ordered or positioned at a certain level relative to another in a ranking or hierarchy.
-
E.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.