Triple
T16702473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozilla Messaging |
E405885
|
entity |
| Predicate | programmingLanguageUsed |
P1592
|
FINISHED |
| Object | XUL |
E405892
|
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: XUL | Statement: [Mozilla Messaging, programmingLanguageUsed, XUL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XUL Context triple: [Mozilla Messaging, programmingLanguageUsed, XUL]
-
A.
XUL user interface language
chosen
XUL user interface language is an XML-based markup language used to define the user interfaces of Mozilla applications such as Firefox.
-
B.
XPCOM
XPCOM is Mozilla’s cross-platform component object model framework that was historically used to build and extend functionality in applications like Firefox.
-
C.
XHTML
XHTML is a reformulation of HTML as an XML-based markup language designed to create structured, standards-compliant web pages.
-
D.
XSLT
XSLT is a language for transforming XML documents into other formats such as XML, HTML, or plain text using template-based rules.
-
E.
XAML
XAML is a declarative XML-based markup language used primarily for designing user interfaces in Microsoft .NET applications, especially on Windows.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e383326d7081909ef4c3b724876513 |
completed | April 18, 2026, 1:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0091a0dee08190a67ed5df2008c91e |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.