Triple
T28731840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napoleon gun-howitzer |
E730680
|
entity |
| Predicate | couldFire |
P58412
|
FINISHED |
| Object | solid shot |
—
|
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: solid shot | Statement: [Napoleon gun-howitzer, couldFire, solid shot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldFire Context triple: [Napoleon gun-howitzer, couldFire, solid shot]
-
A.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
B.
designedToFire
chosen
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
C.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
-
D.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
-
E.
couldIssue
Indicates that one entity has the authority or ability to issue something (such as a document, command, or resource) to 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:58 a.m.