Triple
T4352451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander Field Army |
E98058
|
entity |
| Predicate | militaryRankOfHolder |
P342
|
FINISHED |
| Object | Lieutenant General |
—
|
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: Lieutenant General | Statement: [Commander Field Army, militaryRankOfHolder, Lieutenant General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankOfHolder Context triple: [Commander Field Army, militaryRankOfHolder, Lieutenant General]
-
A.
militaryRank
chosen
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
C.
firstHolderMilitaryRank
Indicates that the subject entity holds or held the earliest or initial military rank associated with the referenced entity.
-
D.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
-
E.
militaryRankOfPrecedence
Indicates the relative seniority or priority order of a military rank compared to other ranks.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.