Triple
T266788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Affordability Report |
E5746
|
entity |
| Predicate | availableFrom |
P1985
|
FINISHED |
| Object | World Wide Web Foundation website |
—
|
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: World Wide Web Foundation website | Statement: [Affordability Report, availableFrom, World Wide Web Foundation website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableFrom Context triple: [Affordability Report, availableFrom, World Wide Web Foundation website]
-
A.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
B.
listedOn
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
-
C.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
D.
accessibleFrom
chosen
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
E.
purchasedFrom
Indicates that one entity bought or acquired something from another entity as the seller or source.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d90bab48190b3ef97a451653b7f |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.