Triple
T25368914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tor-M2E |
E632879
|
entity |
| Predicate | simultaneousEngagementCapability |
P139673
|
FINISHED |
| Object | can engage multiple targets simultaneously |
—
|
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: can engage multiple targets simultaneously | Statement: [Tor-M2E, simultaneousEngagementCapability, can engage multiple targets simultaneously]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: simultaneousEngagementCapability Context triple: [Tor-M2E, simultaneousEngagementCapability, can engage multiple targets simultaneously]
-
A.
canTrackTargetsSimultaneously
chosen
Indicates the ability of an entity to follow or monitor multiple targets at the same time.
-
B.
designedToFireSimultaneously
Indicates that multiple entities are configured or intended to operate or be activated at the same time.
-
C.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
-
E.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a110e8148190883924cfb6b242c4 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:38 p.m.