Triple
T353935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldWideWeb |
E7502
|
entity |
| Predicate | documentation |
P4310
|
FINISHED |
| Object | described in early CERN web documentation |
—
|
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: described in early CERN web documentation | Statement: [WorldWideWeb, documentation, described in early CERN web documentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentation Context triple: [WorldWideWeb, documentation, described in early CERN web documentation]
-
A.
documentedBy
chosen
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
B.
usedDocument
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
C.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
D.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
E.
draft
Indicates that one entity prepares an initial or preliminary version of something, typically a document, plan, or design, which may be revised later.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb80f524819093f4c2c18c3d615f |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.