Triple
T35560990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift BAT |
E1027634
|
entity |
| Predicate | onboardSpacecraft |
P64491
|
FINISHED |
| Object | Swift Gamma-Ray Burst Explorer |
—
|
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: Swift Gamma-Ray Burst Explorer | Statement: [Swift BAT, onboardSpacecraft, Swift Gamma-Ray Burst Explorer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardSpacecraft Context triple: [Swift BAT, onboardSpacecraft, Swift Gamma-Ray Burst Explorer]
-
A.
aboardSpacecraft
chosen
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
B.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
-
C.
usesSpacecraft
Indicates that one entity operates, employs, or relies on a spacecraft to perform an action or fulfill a function in relation to another entity or context.
-
D.
selectedAsAstronaut
Indicates that an individual has been formally chosen to serve as an astronaut, typically through an official selection process.
-
E.
spaceflightParticipant
Indicates that an entity takes part in a spaceflight mission, typically as a non-professional or guest participant rather than as career crew.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.