Triple
T32156208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Launch Complex 37B |
E821297
|
entity |
| Predicate | primaryMissionTypes |
P22637
|
FINISHED |
| Object | defense payloads |
—
|
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: defense payloads | Statement: [Space Launch Complex 37B, primaryMissionTypes, defense payloads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMissionTypes Context triple: [Space Launch Complex 37B, primaryMissionTypes, defense payloads]
-
A.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
B.
primaryMissions
Indicates the main missions or core objectives assigned to or undertaken by an entity.
-
C.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
-
D.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
E.
primaryMissionDependency
Indicates that one mission’s success, initiation, or continuation depends directly on the completion or outcome of another mission.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:32 a.m.