Triple
T29971877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 2 |
E761337
|
entity |
| Predicate | notableCrewFact |
P8229
|
FINISHED |
| Object | Gherman Titov became the second human in orbit |
—
|
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: Gherman Titov became the second human in orbit | Statement: [Vostok 2, notableCrewFact, Gherman Titov became the second human in orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCrewFact Context triple: [Vostok 2, notableCrewFact, Gherman Titov became the second human in orbit]
-
A.
hasNotableCrewMember
Indicates that an entity is associated with a crew member who is considered notable or distinguished in some way.
-
B.
notableProductionFact
Indicates a noteworthy or distinctive fact about how something was produced, created, or manufactured.
-
C.
notableFact
chosen
Indicates that there exists a particularly significant or noteworthy fact or piece of information associated with the subject.
-
D.
featureCrew
Indicates that a particular crew member is highlighted or designated as a featured participant within a crew-related context.
-
E.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:32 p.m.