Triple
T12574104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Military Academy |
E273661
|
entity |
| Predicate | hasCommandant |
P105487
|
FINISHED |
| Object | senior Pakistan Army officer |
—
|
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: senior Pakistan Army officer | Statement: [Pakistan Military Academy, hasCommandant, senior Pakistan Army officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommandant Context triple: [Pakistan Military Academy, hasCommandant, senior Pakistan Army officer]
-
A.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
C.
wasCommandantOf
Indicates that one entity served as the commandant (chief commanding officer) of another entity, typically a military unit, institution, or facility.
-
D.
adoptedByCommandant
Indicates that an entity has been formally accepted or taken under the authority or responsibility of a commandant.
-
E.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
- F. None of above. chosen
Provenance (4 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d9550af6d48190a40e349ed0424be3 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 4:44 p.m.