Triple
T6444944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury-Atlas 7 |
E138317
|
entity |
| Predicate | launchMassCategory |
P35736
|
FINISHED |
| Object | crew capsule-class mission |
—
|
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: crew capsule-class mission | Statement: [Mercury-Atlas 7, launchMassCategory, crew capsule-class mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchMassCategory Context triple: [Mercury-Atlas 7, launchMassCategory, crew capsule-class mission]
-
A.
launchMass
Indicates the total mass of an object or payload at the moment it is launched.
-
B.
launchMassClassification
chosen
Indicates the classification or categorization of an object's launch based on its mass.
-
C.
launchMechanism
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
-
D.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
E.
launchVehicleRole
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698d866c81909ef3e0a53833ff7d |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.