Triple
T8602596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFF-8484 |
E203714
|
entity |
| Predicate | connectorLocation |
P83575
|
FINISHED |
| Object | inside computer chassis |
—
|
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: inside computer chassis | Statement: [SFF-8484, connectorLocation, inside computer chassis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectorLocation Context triple: [SFF-8484, connectorLocation, inside computer chassis]
-
A.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
-
B.
busConnectorLocation
chosen
Indicates the physical position or placement of a bus connector relative to the system or components it connects.
-
C.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
D.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
E.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46da609881909a6d851915e8df14 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.