Triple
T20723767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curtis L. Brown Jr. |
E509382
|
entity |
| Predicate | spaceShuttleMissionRole |
P21471
|
FINISHED |
| Object | pilot on STS-47 |
—
|
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: pilot on STS-47 | Statement: [Curtis L. Brown Jr., spaceShuttleMissionRole, pilot on STS-47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceShuttleMissionRole Context triple: [Curtis L. Brown Jr., spaceShuttleMissionRole, pilot on STS-47]
-
A.
spaceStationRole
Indicates the functional role or duty an entity has in relation to a space station.
-
B.
spacecraftRole
Indicates the functional role or mission purpose that a spacecraft serves within a spaceflight activity or system.
-
C.
missionSpecialist
chosen
Indicates that an entity serves in the role of a mission specialist in relation to a particular mission or spaceflight.
-
D.
roleInSpaceX
Indicates that one entity holds or has held a specific role, position, or function within the organization SpaceX.
-
E.
spaceportRole
Indicates the functional role or capacity an entity has in relation to a spaceport (e.g., operator, facility type, or service 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e59b2081909fb6c29cb5018bb4 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:28 p.m.