Triple
T33840292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibo Pressurized Module |
E867340
|
entity |
| Predicate | attachedToNode |
P10139
|
FINISHED |
| Object | Harmony |
—
|
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: Harmony | Statement: [Kibo Pressurized Module, attachedToNode, Harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachedToNode Context triple: [Kibo Pressurized Module, attachedToNode, Harmony]
-
A.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
attachesUsing
Indicates that one entity becomes fastened, connected, or secured to another by means of a specified tool, mechanism, or method.
-
C.
associatedWithElement
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
-
D.
relatedToDetachment
Indicates a relationship in which one entity is associated with the act, state, or process of separating, disengaging, or being removed from another entity or context.
-
E.
permanentlyAttachedSince
Indicates that one entity has been fixed or joined to another in a way intended to be lasting, starting from a specific point in time.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7004e55988190a2d35d4a95a34610 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.