Triple
T37486110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | چیف آف ایئر اسٹاف |
E931534
|
entity |
| Predicate | typeOfLeadershipRole |
P5518
|
FINISHED |
| Object | اسٹریٹجک ملٹری لیڈر شپ رول |
—
|
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: اسٹریٹجک ملٹری لیڈر شپ رول | Statement: [چیف آف ایئر اسٹاف, typeOfLeadershipRole, اسٹریٹجک ملٹری لیڈر شپ رول]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLeadershipRole Context triple: [چیف آف ایئر اسٹاف, typeOfLeadershipRole, اسٹریٹجک ملٹری لیڈر شپ رول]
-
A.
hasTypeOfLeadership
Indicates that an entity possesses or is characterized by a specific style or form of leadership.
-
B.
leadershipRoleOn
Indicates that one entity holds a leadership position or role with respect to another entity.
-
C.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
D.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
leaderType
Indicates the specific role or category of leadership that an entity holds within an organization, group, or context.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:17 p.m.