Triple
T31275979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Complex 13 |
E797515
|
entity |
| Predicate | repurposedFor |
P47023
|
FINISHED |
| Object | commercial launch operations |
—
|
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: commercial launch operations | Statement: [Launch Complex 13, repurposedFor, commercial launch operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repurposedFor Context triple: [Launch Complex 13, repurposedFor, commercial launch operations]
-
A.
laterRepurposedFor
chosen
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
B.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
relocatedForPurpose
Indicates that an entity moved from one location to another specifically to fulfill or pursue a particular purpose or objective.
-
E.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.