Triple
T37442824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCSS |
E930464
|
entity |
| Predicate | usedOnPayloadClass |
P187823
|
FINISHED |
| Object | military communications satellites |
—
|
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: military communications satellites | Statement: [DCSS, usedOnPayloadClass, military communications satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnPayloadClass Context triple: [DCSS, usedOnPayloadClass, military communications satellites]
-
A.
usedByClass
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
-
B.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
C.
usedWithType
Indicates that something is typically or appropriately used together with items of a specified type.
-
D.
isPrototypeOfClassUsedIn
Indicates that one class serves as the prototype or template for another class that is used within a given context or system.
-
E.
usedOnPart
Indicates that something is applied to, operates on, or is intended for use with a specific part of a larger object or system.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.