Triple
T20746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Wide Web |
E411
|
entity |
| Predicate | firstWebsiteLaunched |
P180
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [World Wide Web, firstWebsiteLaunched, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWebsiteLaunched Context triple: [World Wide Web, firstWebsiteLaunched, 1991]
-
A.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
developedAt
Indicates the place or location where something was created, built, or developed.
-
C.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
groundbreakingDate
Indicates the date on which construction officially began for a building, structure, or project (i.e., when ground was first broken).
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246f7bd30819085f751c41f6f029e |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a246526f5881909bc2a46e978bd082 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.