Triple
T5606377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mons Meg |
E147242
|
entity |
| Predicate | artilleryCaliber |
P6076
|
FINISHED |
| Object | about 510 millimetres |
—
|
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: about 510 millimetres | Statement: [Mons Meg, artilleryCaliber, about 510 millimetres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artilleryCaliber Context triple: [Mons Meg, artilleryCaliber, about 510 millimetres]
-
A.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
B.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
C.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
D.
artilleryUsedIn
Indicates that a particular piece or type of artillery is employed or deployed in a specific event, operation, or context.
-
E.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fbb8748190841e5e09db3feef1 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.