Triple
T20542723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirty-Five New Guys |
E504387
|
entity |
| Predicate | numberOfAstronauts |
P8794
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [Thirty-Five New Guys, numberOfAstronauts, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAstronauts Context triple: [Thirty-Five New Guys, numberOfAstronauts, 35]
-
A.
numberOfAstronautsSelected
Indicates the quantity of astronauts that have been chosen or selected in a given context or selection process.
-
B.
isAstronautOf
Indicates that a person serves as an astronaut who is a member of, or assigned to, a particular space agency, mission, or spacecraft.
-
C.
totalAstronautsFlown
chosen
Indicates the total number of astronauts who have flown on a particular mission, vehicle, or program.
-
D.
astronautGroup
Indicates a relationship where multiple individuals are grouped together as astronauts, typically forming a crew or team for space-related missions or activities.
-
E.
associatedWithAstronaut
Indicates a relationship in which an entity has a connection, link, or involvement with an astronaut.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a293feac8190b27848b64f2db1fe |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.