Triple
T11187796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Pad 36A |
E264717
|
entity |
| Predicate | launchesBegan |
P86808
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Launch Pad 36A, launchesBegan, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchesBegan Context triple: [Launch Pad 36A, launchesBegan, 1960s]
-
A.
launchesConducted
Indicates that one entity has carried out or executed one or more launch events involving another entity or object.
-
B.
launchesOn
chosen
Indicates that one entity initiates or begins another entity (such as a process, event, or object) at a specific time or on a specific date.
-
C.
launchesConductedFor
Indicates that one entity performs or carries out launches on behalf of, or for the benefit of, another entity.
-
D.
launchesFrom
Indicates that an object or agent initiates its movement, operation, or departure starting at a specified location or source.
-
E.
launchesTo
Indicates that one entity initiates the sending or propulsion of another entity toward a specific destination or into a particular trajectory.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ad143481908d5dacc95837ecfd |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.