Triple
T4072857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drawa fire control system |
E86687
|
entity |
| Predicate | controlDomain |
P53339
|
FINISHED |
| Object | gunnery control |
—
|
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: gunnery control | Statement: [Drawa fire control system, controlDomain, gunnery control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlDomain Context triple: [Drawa fire control system, controlDomain, gunnery control]
-
A.
transportDomain
Indicates a relationship where an entity operates or functions within the domain or context of transportation activities or systems.
-
B.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
C.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
D.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
E.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc22be988190a2b6575d4f5e0f7b |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:38 p.m.