Triple
T14757285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patton's Own |
E346761
|
entity |
| Predicate | associatedCommanderRank |
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: [Patton's Own, associatedCommanderRank, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCommanderRank Context triple: [Patton's Own, associatedCommanderRank, General]
-
A.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
B.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
-
C.
governmentCommanderRank
Indicates that an individual holds a specific rank within a government’s command or leadership hierarchy.
-
D.
hasRankForCommandant
Indicates that an entity holds the specific rank required to serve as a commandant.
-
E.
airCommanderRank
Indicates that one entity holds the rank or position of air commander relative to another entity (such as a force, unit, or operation).
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7ef0fd48190bd4a8af128ef274c |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.