Triple
T11274856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7.5 cm StuK 37 L/24 |
E266907
|
entity |
| Predicate | intendedTargetType |
P9903
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [7.5 cm StuK 37 L/24, intendedTargetType, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedTargetType Context triple: [7.5 cm StuK 37 L/24, intendedTargetType, infantry]
-
A.
intendedTargetContext
Indicates the context, situation, or setting that an action, message, or object is specifically designed or meant to be used in or directed toward.
-
B.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
C.
primaryTargetType
chosen
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
E.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e966cb4c8190bc410d7e623e54db |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.