Triple
T34748587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astronaut Group 21 |
E1001704
|
entity |
| Predicate | includesEngineers |
P205542
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NASA Astronaut Group 21, includesEngineers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEngineers Context triple: [NASA Astronaut Group 21, includesEngineers, true]
-
A.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
B.
stateEngineeringCategory
Indicates that an entity is classified under a specific category within the field of engineering as defined or regulated by a state.
-
C.
laterEngineer
Indicates that one entity becomes an engineer at a later time than another entity.
-
D.
engineeringWork
Indicates a relationship where an entity performs, produces, or is involved in an engineering-related task, project, or output.
-
E.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
- F. None of above. chosen
Provenance (4 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.