Triple
T34507455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Guidance Software |
E885924
|
entity |
| Predicate | usedInterfaceDevice |
P9919
|
FINISHED |
| Object | DSKY |
E885922
|
NE 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: DSKY | Statement: [Apollo Guidance Software, usedInterfaceDevice, DSKY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInterfaceDevice Context triple: [Apollo Guidance Software, usedInterfaceDevice, DSKY]
-
A.
interfaceDevice
Indicates that one entity serves as an interface device through which another entity interacts, communicates, or connects with a system or environment.
-
B.
usesDevice
chosen
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
-
D.
usedAsDeviceFor
Indicates that one entity functions as a tool, instrument, or device for performing an action or achieving a particular purpose for another entity.
-
E.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
- F. None of above.
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3736160eb4819091d21826f898332b |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: May 1, 2026, 2:01 a.m.