Triple
T32708730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UserTransaction |
E836341
|
entity |
| Predicate | begin()Throws |
P174821
|
FINISHED |
| Object | jakarta.transaction.NotSupportedException |
—
|
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: jakarta.transaction.NotSupportedException | Statement: [UserTransaction, begin()Throws, jakarta.transaction.NotSupportedException]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: begin()Throws Context triple: [UserTransaction, begin()Throws, jakarta.transaction.NotSupportedException]
-
A.
mởĐầuBằng
Indicates that one entity begins or starts with another entity (e.g., a text, sequence, or event opens with a specified element).
-
B.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
C.
exportStart
Indicates the point in time or event at which an export process or outbound transfer of goods, data, or resources begins.
-
D.
useBegan
Indicates that an entity initiated or started using another entity or resource at a particular point in time.
-
E.
startMethod
Indicates that one entity initiates or begins the execution of a method associated with 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c87bf9c481908804bd231d60cd30 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.