Triple
T13256481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Complex 39 Press Site |
E315669
|
entity |
| Predicate | distanceToLaunchPads |
P53174
|
FINISHED |
| Object | several kilometers from Launch Pad 39A |
—
|
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: several kilometers from Launch Pad 39A | Statement: [Launch Complex 39 Press Site, distanceToLaunchPads, several kilometers from Launch Pad 39A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLaunchPads Context triple: [Launch Complex 39 Press Site, distanceToLaunchPads, several kilometers from Launch Pad 39A]
-
A.
launchPadsCount
Indicates the number of launch pads associated with or available at a given entity or location.
-
B.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
C.
blockhouseDistanceFromPad
Indicates the measured distance between a blockhouse and a launch pad.
-
D.
distanceToRailhead
Indicates the measured distance between a location or object and the nearest railhead (rail transport access point).
-
E.
proximityToLandmark
chosen
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.