Triple
T994072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Candidate Recommendation |
E21454
|
entity |
| Predicate | webPage |
P21673
|
FINISHED |
| Object | https://www.w3.org/Consortium/Process/ |
—
|
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: https://www.w3.org/Consortium/Process/ | Statement: [W3C Candidate Recommendation, webPage, https://www.w3.org/Consortium/Process/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webPage Context triple: [W3C Candidate Recommendation, webPage, https://www.w3.org/Consortium/Process/]
-
A.
website
Indicates that one entity is the official website or web presence associated with another entity.
-
B.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
C.
pages
Indicates that one entity consists of or contains a certain number of pages, or that a specific page-related attribute is associated with it.
-
D.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
E.
mainIndex
Indicates that one entity serves as the primary or central index or reference point for another entity within a structured system.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c5e16881908cd5f7ba2fcd5084 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2af071c819086c374a16307dfe0 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b30efd2c8190b780a6dee086d0aa |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:41 p.m.