Triple
T27734890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IO.IOException |
E697506
|
entity |
| Predicate | baseClassOf |
P32473
|
FINISHED |
| Object | System.IO.EndOfStreamException |
—
|
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: System.IO.EndOfStreamException | Statement: [System.IO.IOException, baseClassOf, System.IO.EndOfStreamException]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseClassOf Context triple: [System.IO.IOException, baseClassOf, System.IO.EndOfStreamException]
-
A.
topClassOf
Indicates that one class is the most general or highest-level superclass from which another class (or set of classes) ultimately derives.
-
B.
baseType
chosen
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
C.
isClassOf
Indicates that one entity is a class or category to which another entity belongs or is an instance of.
-
D.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
E.
classBelow
Indicates that one class is positioned lower than another in a hierarchy, ordering, or structural arrangement.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369fa1d88190ac40370ec4fa185e |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:12 p.m.