Triple
T20895914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WR-40 Langusta |
E514533
|
entity |
| Predicate | canFireSalvo |
P58413
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WR-40 Langusta, canFireSalvo, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canFireSalvo Context triple: [WR-40 Langusta, canFireSalvo, yes]
-
A.
designedToFireSimultaneously
chosen
Indicates that multiple entities are configured or intended to operate or be activated at the same time.
-
B.
courseOfFire
Indicates the specific sequence, arrangement, and conditions of shots or stages that define how a shooting exercise or match is to be conducted.
-
C.
directFireRequirement
Indicates that one entity specifies or imposes the conditions, resources, or capabilities needed for another entity to conduct direct-fire operations.
-
D.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
E.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d06233588190942493b709e30820 |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.