Triple
T35724612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N1 lunar rocket program |
E1032571
|
entity |
| Predicate | intendedLunarOrbitCrew |
P195658
|
FINISHED |
| Object | 1 cosmonaut in lunar 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: 1 cosmonaut in lunar orbit | Statement: [N1 lunar rocket program, intendedLunarOrbitCrew, 1 cosmonaut in lunar orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedLunarOrbitCrew Context triple: [N1 lunar rocket program, intendedLunarOrbitCrew, 1 cosmonaut in lunar orbit]
-
A.
intendedLunarLandingCrew
Indicates the relationship where a person or group is designated as the planned crew for a specific lunar landing mission.
-
B.
orbitsCrewedMission
Indicates that a crewed space mission travels around and remains in orbit of a specified celestial body or object.
-
C.
lunarMission
Indicates a mission or operation specifically directed toward exploring, studying, or traveling to the Moon.
-
D.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
E.
crewMemberInOrbit
Indicates that a person is serving as a crew member aboard a spacecraft or station that is currently in orbit.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: May 3, 2026, 4:05 p.m.