Triple
T26726856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMU backpack |
E673857
|
entity |
| Predicate | firstUsedInMission |
P53282
|
FINISHED |
| Object | STS-41-B |
—
|
NE NERFINISHED |
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: STS-41-B | Statement: [MMU backpack, firstUsedInMission, STS-41-B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedInMission Context triple: [MMU backpack, firstUsedInMission, STS-41-B]
-
A.
introducedAsMission
Indicates that one entity is presented or designated to another entity specifically in the context of a mission or assigned task.
-
B.
usedByMission
chosen
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
C.
firstUsedInGame
Indicates the game in which something (such as an item, mechanic, or concept) was first introduced or appeared.
-
D.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
E.
appearsInMission
Indicates that an entity participates in, is featured in, or occurs within a particular mission.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 27, 2026, 3:43 a.m.