Triple
T29392054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPI |
E745388
|
entity |
| Predicate | addressingMethod |
P169680
|
FINISHED |
| Object | chip select lines per slave |
—
|
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: chip select lines per slave | Statement: [SPI, addressingMethod, chip select lines per slave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressingMethod Context triple: [SPI, addressingMethod, chip select lines per slave]
-
A.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
B.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
C.
addressedFor
Indicates that something is directed, designated, or intended for a particular recipient or target.
-
D.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
E.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
- F. None of above. chosen
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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 28, 2026, 2:43 p.m.