Triple
T34954750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVI |
E1008096
|
entity |
| Predicate | typicallyConvertedTo |
P631
|
FINISHED |
| Object | PostScript |
E30048
|
NE 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: PostScript | Statement: [DVI, typicallyConvertedTo, PostScript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyConvertedTo Context triple: [DVI, typicallyConvertedTo, PostScript]
-
A.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
B.
convertsTo
chosen
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
C.
someConvertedTo
Indicates that a portion of one entity has been transformed or changed into another entity.
-
D.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
-
E.
hasConvertedTo
Indicates that an entity has changed its previous state, status, form, or affiliation into a new one.
- F. None of above.
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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8cc30c48190b836891286c75e15 |
completed | June 21, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.