Triple
T36960474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Cannon |
E914293
|
entity |
| Predicate | firingSound |
P187453
|
FINISHED |
| Object | automatic ballistic weapon sound |
—
|
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: automatic ballistic weapon sound | Statement: [Heavy Cannon, firingSound, automatic ballistic weapon sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingSound Context triple: [Heavy Cannon, firingSound, automatic ballistic weapon sound]
-
A.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
-
B.
firingPlatform
Indicates a platform or structure from which a weapon or projectile is launched or fired.
-
C.
firingDirection
Indicates the direction or trajectory along which a firing action (such as shooting or launching a projectile) is aimed or executed.
-
D.
soundOfHorn
Indicates that an entity produces, emits, or is associated with the sound made by a horn.
-
E.
firingCharacteristic
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:13 p.m.