Triple
T22400496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 45th Indian Infantry Brigade |
E553743
|
entity |
| Predicate | hasMilitaryUnitNumber |
P113166
|
FINISHED |
| Object | 45 |
—
|
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: 45 | Statement: [45th Indian Infantry Brigade, hasMilitaryUnitNumber, 45]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryUnitNumber Context triple: [45th Indian Infantry Brigade, hasMilitaryUnitNumber, 45]
-
A.
hasRegimentNumber
chosen
Indicates that an entity (such as a military unit) is assigned a specific regiment number as its identifying designation.
-
B.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
C.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
militaryServiceNumber
Indicates the unique identification number assigned to an individual for tracking their record in a military service context.
-
E.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b39c908190a735aa860d733869 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.