Triple
T14087062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDDL |
E339023
|
entity |
| Predicate | sourceCodeAvailabilityRequirement |
P92547
|
FINISHED |
| Object | for covered files only |
—
|
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: for covered files only | Statement: [CDDL, sourceCodeAvailabilityRequirement, for covered files only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceCodeAvailabilityRequirement Context triple: [CDDL, sourceCodeAvailabilityRequirement, for covered files only]
-
A.
sourceCodeReleased
Indicates that the source code for a software project or component has been made publicly available or otherwise released for access.
-
B.
requiresSourceCodeDisclosure
chosen
Indicates that one party is obligated to make the underlying source code available or visible to another party under specified conditions.
-
C.
sourceCodeLicense
Indicates the legal license under which a piece of source code is distributed or made available.
-
D.
sourceCodeReleasedBy
Indicates that the source code of a software or project has been made publicly available by a specific releasing entity.
-
E.
sourceAvailable
Indicates that the underlying source code or origin of an entity is accessible or obtainable.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5edff1b881909ea56dc2429ef2dd |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.