Triple
T27734559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IO.BinaryWriter |
E697500
|
entity |
| Predicate | propertyType(BaseStream) |
P166453
|
FINISHED |
| Object | System.IO.Stream |
—
|
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.Stream | Statement: [System.IO.BinaryWriter, propertyType(BaseStream), System.IO.Stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType(BaseStream) Context triple: [System.IO.BinaryWriter, propertyType(BaseStream), System.IO.Stream]
-
A.
bitstreamType
Indicates the specific format or category of a given bitstream within a digital system or data context.
-
B.
propertyType(Name)
chosen
Indicates that an entity has a specific type or category of property identified by Name.
-
C.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
D.
propertyType(Namespace)
Indicates that a given entity is classified as a specific type of property within the referenced namespace.
-
E.
staticPropertyType
Indicates that the relationship specifies the type or category of a property that is fixed and does not change over time.
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 3:12 p.m.