Triple
T10502428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-400 |
E247703
|
entity |
| Predicate | missionPatchStatus |
P94517
|
FINISHED |
| Object | no official flown patch |
—
|
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: no official flown patch | Statement: [STS-400, missionPatchStatus, no official flown patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPatchStatus Context triple: [STS-400, missionPatchStatus, no official flown patch]
-
A.
missionPatch
Indicates that an entity serves as the official emblem or insignia associated with a particular mission.
-
B.
missionPatchFeature
Indicates that one entity features or includes another as a design element on a mission patch.
-
C.
missionPatchShape
Indicates the geometric form or outline that a mission’s official patch or emblem takes.
-
D.
missionPatchDesigner
Indicates that one entity is the designer or creator of the mission patch associated with another entity (typically a space mission).
-
E.
missionNumber
Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099c6a848190bf1d5361e9e61108 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:25 p.m.