Triple
T11419698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computerworld |
E270585
|
entity |
| Predicate | operatesOnTheWebAt |
P39688
|
FINISHED |
| Object | https://www.computerworld.com |
—
|
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.computerworld.com | Statement: [Computerworld, operatesOnTheWebAt, https://www.computerworld.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnTheWebAt Context triple: [Computerworld, operatesOnTheWebAt, https://www.computerworld.com]
-
A.
operatedWebsite
chosen
Indicates that one entity runs, manages, or controls the functioning of a particular website.
-
B.
siteOperator
Indicates that one entity is responsible for operating, managing, or running a particular site or facility.
-
C.
usedOnWebsites
Indicates that something is employed or implemented as part of the content, functionality, or infrastructure of websites.
-
D.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
E.
operatesOnSiteType
Indicates that an entity conducts its operations or activities at, or in association with, a specified type of site or location.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b20ce08190befc98379b879985 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.