Triple
T1793527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EJB container |
E39550
|
entity |
| Predicate | abstracts |
P31986
|
FINISHED |
| Object | low-level system services from EJBs |
—
|
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: low-level system services from EJBs | Statement: [EJB container, abstracts, low-level system services from EJBs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstracts Context triple: [EJB container, abstracts, low-level system services from EJBs]
-
A.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another entity.
-
B.
abridgedIn
Indicates that one entity is a shortened or condensed version of the content found within another entity.
-
C.
article2ContentSummary
Indicates that one article serves as a content summary or condensed representation of another article.
-
D.
researchContribution
Indicates that an entity has produced or participated in creating new knowledge, findings, or innovations within a research context.
-
E.
article1ContentSummary
Indicates a brief, condensed representation of the main points or key information contained in the first article’s content.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab61b5c8988190bb2b46182a4eb5b4 |
completed | March 6, 2026, 11:22 p.m. |
Created at: March 4, 2026, 7:32 p.m.