Triple
T37555527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafette 34 tripod |
E933686
|
entity |
| Predicate | allowsOperationMode |
P119199
|
FINISHED |
| Object | indirect fire |
—
|
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: indirect fire | Statement: [Lafette 34 tripod, allowsOperationMode, indirect fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsOperationMode Context triple: [Lafette 34 tripod, allowsOperationMode, indirect fire]
-
A.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
B.
supportsOperationsWith
Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
-
C.
operationSupported
Indicates that a particular operation is available and can be performed or handled by a given entity or system.
-
D.
availableInMode
chosen
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
E.
canOperateAt
Indicates that one entity has the capability, permission, or suitability to function or perform its role at, within, or under the conditions of another entity or context.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:17 p.m.