Triple
T16424697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Gerst |
E398910
|
entity |
| Predicate | performedResearchOn |
P108399
|
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: [Alexander Gerst, performedResearchOn, microgravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedResearchOn Context triple: [Alexander Gerst, performedResearchOn, microgravity]
-
A.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
B.
publishedResearchOn
Indicates that an entity has authored and made publicly available scholarly or scientific work concerning a particular subject or topic.
-
C.
hasResearched
chosen
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
D.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
E.
coResearcher
Indicates that two or more individuals collaborate as peers on the same research work or project.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f9da9081908dadbdac4b2d38ec |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.