Triple
T4786469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double-Barreled Cannon |
E106490
|
entity |
| Predicate | designedToFire |
P58412
|
FINISHED |
| Object | chained cannonballs |
—
|
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: chained cannonballs | Statement: [Double-Barreled Cannon, designedToFire, chained cannonballs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToFire Context triple: [Double-Barreled Cannon, designedToFire, chained cannonballs]
-
A.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
B.
shoulderFired
Indicates that a weapon is designed to be aimed and discharged from the operator’s shoulder.
-
C.
firingDirection
Indicates the direction or trajectory along which a firing action (such as shooting or launching a projectile) is aimed or executed.
-
D.
designedToDefeat
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
E.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65d8f9d881909c24340b8dc6a104 |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.