Triple
T35724610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N1 lunar rocket program |
E1032571
|
entity |
| Predicate | intendedCrewSize |
P30694
|
FINISHED |
| Object | 2 cosmonauts |
—
|
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: 2 cosmonauts | Statement: [N1 lunar rocket program, intendedCrewSize, 2 cosmonauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCrewSize Context triple: [N1 lunar rocket program, intendedCrewSize, 2 cosmonauts]
-
A.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
B.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
C.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
D.
crewCount
chosen
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
E.
crewSizeSimulated
Indicates the number of crew members assumed or used in a simulation rather than in a real-world setting.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4:05 p.m.