Triple
T30754871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 3 |
E783054
|
entity |
| Predicate | controllerInterface |
P173242
|
FINISHED |
| Object | DE-9 controller ports |
—
|
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: DE-9 controller ports | Statement: [Genesis 3, controllerInterface, DE-9 controller ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerInterface Context triple: [Genesis 3, controllerInterface, DE-9 controller ports]
-
A.
commandInterface
chosen
Indicates that one entity serves as a control or command interface through which another entity can be directed, configured, or operated.
-
B.
controllerStyle
Indicates the manner or configuration in which a controller operates or is presented in relation to its associated system or interface.
-
C.
controlApp
Indicates that one entity has the ability or authority to operate, manage, or direct the behavior of an application.
-
D.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
E.
controlProtocol
Indicates that one entity governs, regulates, or coordinates the behavior or operations of another according to a defined set of rules or procedures.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 29, 2026, 8:39 p.m.