Triple
T26347780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp |
E662820
|
entity |
| Predicate | includedEdition |
P40815
|
FINISHED |
| Object | OS/2 Warp Connect |
—
|
NE NERFINISHED |
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: OS/2 Warp Connect | Statement: [Warp, includedEdition, OS/2 Warp Connect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedEdition Context triple: [Warp, includedEdition, OS/2 Warp Connect]
-
A.
includedInEdition
chosen
Indicates that one item (such as a work, text, or component) is contained within or forms part of a particular edition.
-
B.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
C.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
D.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
E.
isBonusEditionOf
Indicates that one item is a special bonus version or supplementary edition of another primary item.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 26, 2026, 10:43 p.m.