Triple
T36485607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus External Payload Facility |
E898924
|
entity |
| Predicate | exposesPayloadsTo |
P53531
|
FINISHED |
| Object | microgravity |
—
|
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: microgravity | Statement: [Columbus External Payload Facility, exposesPayloadsTo, microgravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesPayloadsTo Context triple: [Columbus External Payload Facility, exposesPayloadsTo, microgravity]
-
A.
exposesTo
chosen
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
B.
exposedThrough
Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
-
C.
exposesBinary
Indicates that one entity makes a binary executable or file directly available or accessible to another entity or to the public.
-
D.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
E.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.