Triple
T15363830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merville Battery |
E367355
|
entity |
| Predicate | hasArtilleryCaliber |
P118288
|
FINISHED |
| Object | 150 mm |
—
|
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: 150 mm | Statement: [Merville Battery, hasArtilleryCaliber, 150 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtilleryCaliber Context triple: [Merville Battery, hasArtilleryCaliber, 150 mm]
-
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.
hasArtilleryUse
Indicates that one entity employs, operates, or makes use of artillery in relation to another entity or context.
-
D.
artilleryUsedIn
Indicates that a particular piece or type of artillery is employed or deployed in a specific event, operation, or context.
-
E.
artilleryPiecesUsed
Indicates that certain artillery pieces were employed or deployed in a particular action, event, or context.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:18 a.m.