Triple
T14439502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xalan |
E358048
|
entity |
| Predicate | supportsStandard |
P1587
|
FINISHED |
| Object | SAX |
E543058
|
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: SAX | Statement: [Xalan, supportsStandard, SAX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAX Context triple: [Xalan, supportsStandard, SAX]
-
A.
SAX
chosen
SAX (Simple API for XML) is an event-driven, streaming XML parsing interface commonly used for efficiently processing large XML documents in a forward-only manner.
-
B.
StAX
StAX (Streaming API for XML) is a Java-based pull-parsing API that enables efficient, forward-only, stream-oriented processing of XML documents.
-
C.
SGML
SGML (Standard Generalized Markup Language) is a standardized metalanguage for defining markup languages used to structure and describe the content of electronic documents.
-
D.
XML
XML (Extensible Markup Language) is a flexible, text-based markup language designed for structuring, storing, and transporting data in a platform-independent way.
-
E.
xalan
Xalan is an Apache project that provides an XSLT processor for transforming XML documents.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914c1398819090fa2a74d257ba3e |
completed | April 14, 2026, 7:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bd7f46881908df1a1cea7b6af9b |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.