Triple
T25186715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NX-01 |
E630736
|
entity |
| Predicate | launchSiteInUniverse |
P158415
|
FINISHED |
| Object | Orbital Drydock above Earth |
—
|
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: Orbital Drydock above Earth | Statement: [NX-01, launchSiteInUniverse, Orbital Drydock above Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSiteInUniverse Context triple: [NX-01, launchSiteInUniverse, Orbital Drydock above Earth]
-
A.
launchSites
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.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
D.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
E.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
- F. None of above. chosen
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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0aeb588190b3ee13a6c031c223 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 12:44 p.m.