Triple
T14659738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java Portlet Specification |
E344205
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | JavaServer Pages |
E200572
|
NE 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: JavaServer Pages | Statement: [Java Portlet Specification, relatedTo, JavaServer Pages]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JavaServer Pages Context triple: [Java Portlet Specification, relatedTo, JavaServer Pages]
-
A.
Jakarta Server Pages
chosen
Jakarta Server Pages is a Jakarta EE web technology that enables developers to create dynamic, server-side HTML content using Java-based templates.
-
B.
JSP
JSP is the commonly used abbreviation for the Japan Socialist Party, a former major left-wing political party in Japan.
-
C.
Jakarta Server Faces
Jakarta Server Faces is a component-based web framework for building server-side user interfaces in Java enterprise applications.
-
D.
Java servlets
Java servlets are server-side Java programs that extend web servers to handle HTTP requests and generate dynamic web content in Java-based web applications.
-
E.
Java EE
Java EE is a widely used enterprise-grade Java platform specification for building scalable, distributed, and transactional server-side applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51b6a248190a44050c0e0ec2d16 |
completed | April 14, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5e28f848190a3d686bc11336601 |
completed | May 8, 2026, 12:24 p.m. |
Created at: April 10, 2026, 1:27 a.m.