Triple
T28387032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Headquarters, U.S. Army (in concept) |
E719044
|
entity |
| Predicate | envisionedCommanderRank |
P30999
|
FINISHED |
| Object | 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: general | Statement: [General Headquarters, U.S. Army (in concept), envisionedCommanderRank, general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envisionedCommanderRank Context triple: [General Headquarters, U.S. Army (in concept), envisionedCommanderRank, general]
-
A.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
B.
opposingCommanderRank
Indicates that the related entity holds a specific military rank as the commander of the opposing or enemy force in a conflict or engagement.
-
C.
hasRankForCommandant
Indicates that an entity holds the specific rank required to serve as a commandant.
-
D.
commandingOfficerRank
Indicates the military rank held by the officer who has command authority over a given individual or unit.
-
E.
governmentCommanderRank
Indicates that an individual holds a specific rank within a government’s command or leadership 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:10 a.m.