Triple
T33211790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Titan III |
E850181
|
entity |
| Predicate | targetPayload |
P196599
|
FINISHED |
| Object | geostationary 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: geostationary communications satellites | Statement: [Commercial Titan III, targetPayload, geostationary communications satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPayload Context triple: [Commercial Titan III, targetPayload, geostationary communications satellites]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetOfThreat
Indicates that one entity is the recipient or intended victim of a threat made by another entity.
-
C.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
D.
targetsVector
Indicates that one entity is directed toward, aimed at, or focused on another entity represented as a vector (e.g., a direction or target position).
-
E.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
| PDg | Predicate description generation | batch_69fe5d580d7c819097cb18d438b01d08 |
completed | May 8, 2026, 10:02 p.m. |
Created at: May 1, 2026, 1:30 a.m.