Triple
T26426990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule Interchange Format |
E664395
|
entity |
| Predicate | webAddress |
P21673
|
FINISHED |
| Object | https://www.w3.org/2005/rules/wiki/RIF |
—
|
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/2005/rules/wiki/RIF | Statement: [Rule Interchange Format, webAddress, https://www.w3.org/2005/rules/wiki/RIF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webAddress Context triple: [Rule Interchange Format, webAddress, https://www.w3.org/2005/rules/wiki/RIF]
-
A.
website
Indicates that one entity is the official website or web presence associated with another entity.
-
B.
webPage
chosen
Indicates that one entity is a web page associated with, describing, or providing information about another entity.
-
C.
webUse
Indicates that an entity uses or interacts with another entity via the web or through web-based functionality.
-
D.
associatedWebsite
Indicates that one entity has a related or officially connected website represented by the other entity.
-
E.
webType
Indicates the classification or category of a web resource or web-related entity (such as its type, role, or format) within a given context.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611bbb9fc8190b54a32b3bf2152a0 |
completed | May 2, 2026, 3:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:46 p.m.