Triple
T31793358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astronaut Group 18 |
E811526
|
entity |
| Predicate | notableMissionOfMember |
P207521
|
FINISHED |
| Object | STS-135 |
E32708
|
NE 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: STS-135 | Statement: [NASA Astronaut Group 18, notableMissionOfMember, STS-135]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMissionOfMember Context triple: [NASA Astronaut Group 18, notableMissionOfMember, STS-135]
-
A.
notableRoleOfLeader
Indicates that a particular role, position, or office is the most notable or defining one held by a given leader.
-
B.
notableCabinetMember
Indicates that a person has served as a particularly prominent or significant member of a government cabinet.
-
C.
notableCountryRole
Indicates that an entity holds a significant or prominent role, position, or function within a particular country.
-
D.
notableOfficeHolder
Indicates that an entity is a significant or distinguished holder of a particular office or position associated with another entity.
-
E.
hasNotablePoliticalRoleIn
Indicates that an entity holds or has held a significant political position, function, or influence within a specified context or jurisdiction.
- F. None of above. chosen
Provenance (5 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e6596a7108190a242c2cc59ef3bf2 |
completed | June 14, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 11:39 p.m.