Triple
T26312618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Saraighat |
E661866
|
entity |
| Predicate | militaryBranchUsed |
P91149
|
FINISHED |
| Object | Ahom navy |
—
|
NE NERFINISHED |
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: Ahom navy | Statement: [Battle of Saraighat, militaryBranchUsed, Ahom navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchUsed Context triple: [Battle of Saraighat, militaryBranchUsed, Ahom navy]
-
A.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
militaryBranchAssociatedWith
chosen
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
C.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
D.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
E.
militaryBranchDomain
Indicates that one entity serves as the military branch or armed forces component associated with the domain, jurisdiction, or organizational scope of another entity.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 10:23 p.m.