Triple
T576014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTML5 |
E13761
|
entity |
| Predicate | namespaceURI |
P15686
|
FINISHED |
| Object | http://www.w3.org/1999/xhtml |
—
|
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: http://www.w3.org/1999/xhtml | Statement: [HTML5, namespaceURI, http://www.w3.org/1999/xhtml]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namespaceURI Context triple: [HTML5, namespaceURI, http://www.w3.org/1999/xhtml]
-
A.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
B.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
C.
nestName
Indicates that an entity has or is associated with a specific nest’s name.
-
D.
standardPrefix
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
E.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b67395c8190a8046ff7debe9d1f |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.