Triple
T34714169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Astronaut Group 20 |
E1000727
|
entity |
| Predicate | trainingState |
P36516
|
FINISHED |
| Object | Texas |
—
|
NE NERFINISHED |
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: Texas | Statement: [NASA Astronaut Group 20, trainingState, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingState Context triple: [NASA Astronaut Group 20, trainingState, Texas]
-
A.
trainingStatus
chosen
Indicates the current state or phase of an entity within a training or learning process.
-
B.
trainingStartState
Indicates the initial condition or status of an entity at the moment a training process begins.
-
C.
trainingStability
Indicates the degree to which a training process proceeds consistently without large fluctuations, divergence, or instability in its behavior or outcomes.
-
D.
trainingVersion
Indicates that one entity is a specific training iteration, release, or configuration derived from or associated with another entity.
-
E.
trainingUnder
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.