Triple
T1793407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOS/360 |
E39548
|
entity |
| Predicate | outputMedium |
P4793
|
FINISHED |
| Object | line printer |
—
|
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: line printer | Statement: [TOS/360, outputMedium, line printer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputMedium Context triple: [TOS/360, outputMedium, line printer]
-
A.
usedMedium
chosen
Indicates that an action or communication was carried out through a particular medium or channel.
-
B.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
C.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
-
D.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
E.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.