Triple
T30877105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUOS |
E786507
|
entity |
| Predicate | providesCapabilitySimilarTo |
P193781
|
FINISHED |
| Object | smartphone-like connectivity |
—
|
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: smartphone-like connectivity | Statement: [MUOS, providesCapabilitySimilarTo, smartphone-like connectivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesCapabilitySimilarTo Context triple: [MUOS, providesCapabilitySimilarTo, smartphone-like connectivity]
-
A.
providesCapabilityTo
Indicates that one entity enables or equips another entity with a specific capability or functionality.
-
B.
demonstratedCapability
Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
-
C.
associatedCapability
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
-
D.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
E.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: April 29, 2026, 8:48 p.m.