Triple
T27734843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IO.EndOfStreamException |
E697505
|
entity |
| Predicate | typicalAPI |
P201487
|
FINISHED |
| Object | System.IO.BinaryReader |
—
|
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.BinaryReader | Statement: [System.IO.EndOfStreamException, typicalAPI, System.IO.BinaryReader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAPI Context triple: [System.IO.EndOfStreamException, typicalAPI, System.IO.BinaryReader]
-
A.
APIType
Indicates the type or category of an API associated with or used by an entity.
-
B.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
-
C.
typicalEndpoint
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
D.
targetsAPI
Indicates that one entity is designed to interact with, call, or be compatible with a specific API.
-
E.
toolUseExamples
Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
- F. None of above. chosen
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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: April 27, 2026, 3:12 p.m.