Triple
T11656535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DriverManager |
E277023
|
entity |
| Predicate | throwsException |
P100218
|
FINISHED |
| Object | java.sql.SQLException |
—
|
LITERAL 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: java.sql.SQLException | Statement: [DriverManager, throwsException, java.sql.SQLException]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throwsException Context triple: [DriverManager, throwsException, java.sql.SQLException]
-
A.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
B.
throwsPosition
Indicates that one entity performs a throwing action that determines or affects the spatial position of another entity.
-
C.
doesNotProvideExceptionFor
Indicates that one party or rule fails to grant an exemption, special case, or exclusion to another party or situation.
-
D.
hasException
Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
-
E.
hasExceptionConstruct
Indicates that a construct or element is associated with, or defined by, a specific exception-handling construct (such as a try-catch or similar exception mechanism).
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.