Triple
T250793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSV Limiting Factor |
E5141
|
entity |
| Predicate | equippedWith |
P2728
|
FINISHED |
| Object | thrusters for maneuvering at depth |
—
|
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: thrusters for maneuvering at depth | Statement: [DSV Limiting Factor, equippedWith, thrusters for maneuvering at depth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equippedWith Context triple: [DSV Limiting Factor, equippedWith, thrusters for maneuvering at depth]
-
A.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
B.
usesEquipment
chosen
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
C.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
D.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
E.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.