Triple
T27467556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (test orbiter) |
E693215
|
entity |
| Predicate | launchSiteForTests |
P4384
|
FINISHED |
| Object | Edwards Air Force Base |
—
|
NE NERFINISHED |
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: Edwards Air Force Base | Statement: [Enterprise (test orbiter), launchSiteForTests, Edwards Air Force Base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSiteForTests Context triple: [Enterprise (test orbiter), launchSiteForTests, Edwards Air Force Base]
-
A.
launchLocation
Indicates the place or site from which something is launched or set into motion.
-
B.
launchSiteInUniverse
Indicates that a launch site exists or is located within a particular universe or cosmic setting.
-
C.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
D.
usesLaunchSite
chosen
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
E.
launchSiteCode
Indicates the code that identifies the site or location from which a launch takes place.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 12:52 p.m.