Triple
T13002251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTML meta viewport element |
E322196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTML meta element |
C32320
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: HTML meta element Context triple: [HTML meta viewport element, instanceOf, HTML meta element]
-
A.
markup language
A markup language is a system for annotating text or data with tags that define its structure, presentation, or semantics, enabling consistent formatting and processing by software.
-
B.
entity header field
An entity header field is a metadata component in a message (such as HTTP) that describes characteristics of the message body, including its content type, length, encoding, and other entity-specific information.
-
C.
metadata standard
A metadata standard is a structured set of rules and definitions that specify how information about resources should be described, formatted, and shared to ensure consistency, interoperability, and discoverability.
-
D.
HTTP header field
An HTTP header field is a key-value pair in an HTTP message that conveys metadata and control information between a client and server, such as content type, caching policies, and authentication details.
-
E.
markup language standard
A markup language standard is a formally defined set of rules and syntax for structuring, annotating, and representing data or documents in a consistent, interoperable format.
- F. None of above. chosen
Provenance (1 batch)
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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:47 p.m.