Triple
T31582733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VT52 |
E805868
|
entity |
| Predicate | serialStandard |
P144296
|
FINISHED |
| Object | RS-232-compatible |
—
|
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: RS-232-compatible | Statement: [VT52, serialStandard, RS-232-compatible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serialStandard Context triple: [VT52, serialStandard, RS-232-compatible]
-
A.
serialInterface
chosen
Indicates a relationship where data is transmitted between components over a serial communication interface (one bit at a time over a communication line or bus).
-
B.
serialProperty
Indicates that one entity is a property or attribute that is part of a sequential or ordered series associated with another entity.
-
C.
serialModeDescription
Indicates the description or textual explanation of a device’s serial communication mode or configuration.
-
D.
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).
-
E.
binaryStandard
Indicates that something conforms to, or is defined according to, a specific binary encoding or representation standard.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a80a55408190afca2a5c75508088 |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:24 p.m.