Triple
T28998568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta EE MVC frameworks |
E736229
|
entity |
| Predicate | separatesConcern |
P167391
|
FINISHED |
| Object | business logic |
—
|
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: business logic | Statement: [Jakarta EE MVC frameworks, separatesConcern, business logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesConcern Context triple: [Jakarta EE MVC frameworks, separatesConcern, business logic]
-
A.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
B.
separatedFunctionFrom
Indicates that one entity has been detached or removed from performing a particular function or role in relation to another entity.
-
C.
encapsulation
Indicates that one entity encloses, contains, or wraps another entity or set of details within a defined boundary, often hiding internal structure from external access.
-
D.
componentPrinciple
Indicates that one entity serves as a fundamental component or underlying principle that structurally or conceptually supports or governs another entity.
-
E.
separatesPlanningSystemFrom
Indicates that one entity establishes or maintains a clear division between a planning system and another component, layer, or concern.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 9:33 a.m.