Triple
T19515385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Cannon |
E488263
|
entity |
| Predicate | firingPosition |
P74643
|
FINISHED |
| Object | fixed emplacement |
—
|
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: fixed emplacement | Statement: [Tsar Cannon, firingPosition, fixed emplacement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingPosition Context triple: [Tsar Cannon, firingPosition, fixed emplacement]
-
A.
firingDirection
Indicates the direction or trajectory along which a firing action (such as shooting or launching a projectile) is aimed or executed.
-
B.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
-
C.
firingPlatform
chosen
Indicates a platform or structure from which a weapon or projectile is launched or fired.
-
D.
firingCharacteristic
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
-
E.
hasShootingPosition
Indicates that an entity has a designated location or spot from which shooting (e.g., firing a weapon or taking a shot) is performed.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359b90f08190b38359dc9e97e11c |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.