Triple
T36485126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cygnus |
E898914
|
entity |
| Predicate | typicalLaunchSite |
P44497
|
FINISHED |
| Object | Mid-Atlantic Regional Spaceport |
E422356
|
NE 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: Mid-Atlantic Regional Spaceport | Statement: [Cygnus, typicalLaunchSite, Mid-Atlantic Regional Spaceport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLaunchSite Context triple: [Cygnus, typicalLaunchSite, Mid-Atlantic Regional Spaceport]
-
A.
launchSites
chosen
Indicates locations from which an object, mission, or vehicle is launched or initiated.
-
B.
launchSiteCode
Indicates the code that identifies the site or location from which a launch takes place.
-
C.
nearbyLaunchComplex
Indicates that one launch complex is located close to another in physical space.
-
D.
firstSuccessfulLaunchSite
Indicates the launch site where an entity’s first successful launch or mission took place.
-
E.
spaceLaunchDestination
Indicates the target location or body in space toward which a space launch is directed.
- F. None of above.
Provenance (4 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfdefc7081908671067892fda4ae |
completed | June 23, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.