Triple
T5362362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gondal State |
E103050
|
entity |
| Predicate | gunSalute |
P25807
|
FINISHED |
| Object | 11-gun salute |
—
|
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: 11-gun salute | Statement: [Gondal State, gunSalute, 11-gun salute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gunSalute Context triple: [Gondal State, gunSalute, 11-gun salute]
-
A.
ceremonialGunSalute
chosen
Indicates a formal military or state honor in which guns are fired in a prescribed sequence to ceremonially recognize or pay respect to a person, event, or occasion.
-
B.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
-
C.
garrisonDuty
Indicates a relationship where an entity is assigned to stay and defend or guard a specific location as part of its military or protective duties.
-
D.
warSecretary
Indicates that one entity serves as the war secretary (or secretary of war/defense) of another entity, typically a government or state.
-
E.
garrisonSide
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.