Triple
T36312028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2chan |
E894089
|
entity |
| Predicate | hosting |
P162725
|
FINISHED |
| Object | commercial web hosting services |
—
|
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: commercial web hosting services | Statement: [2chan, hosting, commercial web hosting services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hosting Context triple: [2chan, hosting, commercial web hosting services]
-
A.
hostingModel
chosen
Indicates that one entity serves as the environment or platform on which another entity is deployed, run, or made available.
-
B.
hostingLocation
Indicates the place or venue where an event, activity, or entity is being hosted or takes place.
-
C.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
D.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
E.
supportsHosting
Indicates that one entity provides the necessary resources or capabilities for another entity to host or run something (such as an application, service, or content).
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.