Triple
T19586853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java EE 5 |
E490126
|
entity |
| Predicate | majorChange |
P31455
|
FINISHED |
| Object | simplified EJB programming model |
—
|
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: simplified EJB programming model | Statement: [Java EE 5, majorChange, simplified EJB programming model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorChange Context triple: [Java EE 5, majorChange, simplified EJB programming model]
-
A.
majorUpdate
chosen
Indicates that a substantial or significant change or revision has been made to something, typically altering its core features or functionality.
-
B.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
C.
majorOperation
Indicates that one entity performs or undergoes a significant, large-scale, or primary operation or procedure involving another entity or context.
-
D.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
E.
majorRevisionDate
Indicates the date on which an entity underwent a significant or substantial update or revision.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640523d10819091320a61456f6437 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.