Triple
T17635178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G6 howitzer |
E430074
|
entity |
| Predicate | maximumRangeWithBaseBleed |
P14301
|
FINISHED |
| Object | approximately 39 km |
—
|
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: approximately 39 km | Statement: [G6 howitzer, maximumRangeWithBaseBleed, approximately 39 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeWithBaseBleed Context triple: [G6 howitzer, maximumRangeWithBaseBleed, approximately 39 km]
-
A.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
B.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
C.
maximumReach
chosen
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
E.
maximumUsage
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46ddfeb7c8190a369b438e43d47b4 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.