Triple
T617916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akbar |
E14445
|
entity |
| Predicate | militaryAchievement |
P9723
|
FINISHED |
| Object | conquest of Gujarat |
—
|
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: conquest of Gujarat | Statement: [Akbar, militaryAchievement, conquest of Gujarat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryAchievement Context triple: [Akbar, militaryAchievement, conquest of Gujarat]
-
A.
battleHonors
Indicates that an entity has been awarded or is associated with specific honors or distinctions earned through participation in battles or military engagements.
-
B.
peacetimeAward
Indicates that an award or honor is given during a period of peace rather than during wartime or active conflict.
-
C.
isCivilianAward
Indicates that an award is designated for civilians rather than military or combat-related recipients.
-
D.
wartimeAward
Indicates that an entity received an award or honor specifically in the context of wartime or military conflict.
-
E.
militaryMeasure
chosen
Indicates a relationship where an entity undertakes, imposes, or is subject to a specific military-related action, policy, or operational measure.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.