Triple
T353925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldWideWeb |
E7502
|
entity |
| Predicate | sourceCodeAvailability |
P7052
|
FINISHED |
| Object | source code released by CERN |
—
|
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: source code released by CERN | Statement: [WorldWideWeb, sourceCodeAvailability, source code released by CERN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceCodeAvailability Context triple: [WorldWideWeb, sourceCodeAvailability, source code released by CERN]
-
A.
openSource
chosen
Indicates that the subject makes its source code publicly available under a license that allows others to use, modify, and redistribute it.
-
B.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
C.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
D.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
E.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
- 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.