Triple
T33434379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTML Templates |
E856207
|
entity |
| Predicate | associatedDOMInterface |
P93402
|
FINISHED |
| Object | HTMLTemplateElement |
—
|
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: HTMLTemplateElement | Statement: [HTML Templates, associatedDOMInterface, HTMLTemplateElement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDOMInterface Context triple: [HTML Templates, associatedDOMInterface, HTMLTemplateElement]
-
A.
relatedInterface
chosen
Indicates that one interface is associated or connected to another interface in a relevant or dependent way.
-
B.
relatedToInterface
Indicates a relationship where one entity is associated with, concerns, or is relevant to a particular interface.
-
C.
comparedToDOM
Indicates that one entity has been evaluated or measured in relation to another entity serving as a reference or standard.
-
D.
coversInterface
Indicates that one entity provides or implements the functionality defined by a specified interface.
-
E.
associatedWithElement
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
- F. None of above.
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.