Triple
T20542724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirty-Five New Guys |
E504387
|
entity |
| Predicate | isFirstToInclude |
P140482
|
FINISHED |
| Object | American female astronauts |
—
|
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: American female astronauts | Statement: [Thirty-Five New Guys, isFirstToInclude, American female astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstToInclude Context triple: [Thirty-Five New Guys, isFirstToInclude, American female astronauts]
-
A.
initiallyIncluded
Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
-
B.
isFirstInCategory
Indicates that an entity is the earliest or primary member within a defined category or group.
-
C.
isFirstSingleFrom
Indicates that one musical work is the first single released from another work, typically an album or larger recording project.
-
D.
wasFirstOf
Indicates that the subject is the earliest or initial instance in a series, sequence, or group of similar entities or events.
-
E.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
- 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_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. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.