Triple
T27384714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-50 |
E691335
|
entity |
| Predicate | wasFirstUSMLMission |
P162373
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [STS-50, wasFirstUSMLMission, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstUSMLMission Context triple: [STS-50, wasFirstUSMLMission, true]
-
A.
firstSuccessfulDemoMission
Indicates that the mission is the first demonstration mission that achieved its intended success.
-
B.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
C.
firstOperationalCargoMission
Indicates that the subject entity is the earliest or initial cargo mission to be put into operational service for the related program, system, or route.
-
D.
firstRendezvousMission
Indicates that the mission is the first instance in which two or more entities conduct a rendezvous operation.
-
E.
firstOperationalMissionUnderContract
Indicates that the mission is the initial operational mission carried out under a specific contract between the involved parties.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c89b7b88190a8b2af842f5f9cca |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:24 p.m.