Triple
T5705330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carron Company |
E125769
|
entity |
| Predicate | carronadeType |
P19273
|
FINISHED |
| Object | short smoothbore cast-iron naval cannon |
—
|
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: short smoothbore cast-iron naval cannon | Statement: [Carron Company, carronadeType, short smoothbore cast-iron naval cannon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carronadeType Context triple: [Carron Company, carronadeType, short smoothbore cast-iron naval cannon]
-
A.
artilleryType
chosen
Indicates the specific category or kind of artillery associated with an entity or event.
-
B.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
C.
hasSmallCalibreGuns
Indicates that the subject is equipped with or possesses guns of relatively small calibre compared to standard or typical armaments.
-
D.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
E.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02459cd18819080fda0b481d11f08 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.