Triple
T34977738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas program |
E1008726
|
entity |
| Predicate | launchedPayloadType |
P167796
|
FINISHED |
| Object | reconnaissance 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: reconnaissance satellites | Statement: [Atlas program, launchedPayloadType, reconnaissance satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedPayloadType Context triple: [Atlas program, launchedPayloadType, reconnaissance satellites]
-
A.
launchesPayloadType
chosen
Indicates that an entity initiates the deployment or sending of a payload of a specified type.
-
B.
launchesPayloadsFor
Indicates a relationship where one entity (such as a launch vehicle or service) performs launch operations to place another entity’s payloads into space on its behalf.
-
C.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
D.
lastLaunchPayload
Indicates the payload that was carried on the most recent launch associated with the given entity.
-
E.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:01 p.m.