Triple
T21570517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPC6128 |
E532268
|
entity |
| Predicate | serialInterface |
P144296
|
FINISHED |
| Object | optional via expansion |
—
|
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: optional via expansion | Statement: [CPC6128, serialInterface, optional via expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serialInterface Context triple: [CPC6128, serialInterface, optional via expansion]
-
A.
serialProperty
Indicates that one entity is a property or attribute that is part of a sequential or ordered series associated with another entity.
-
B.
serialStudio
Indicates a relationship where an entity is associated with a studio in a serial or recurring production context (e.g., a studio responsible for a series or multiple installments).
-
C.
hasSerialInputPin
Indicates that an entity possesses a pin or connector specifically designated for receiving serial input signals.
-
D.
serialModeDescription
Indicates the description or textual explanation of a device’s serial communication mode or configuration.
-
E.
hasSerialOutputPin
Indicates that an entity is equipped with a pin or connector dedicated to transmitting data via a serial output interface.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cc5c448190887a836f577d01ba |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.