Triple
T18265928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knuth license |
E437482
|
entity |
| Predicate | requiresSourceAvailability |
P92547
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Knuth license, requiresSourceAvailability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSourceAvailability Context triple: [Knuth license, requiresSourceAvailability, true]
-
A.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
-
B.
requiresDataAvailability
Indicates that one entity’s operation, validity, or execution is contingent on the presence, accessibility, or readiness of specific data.
-
C.
sourceAvailable
Indicates that the underlying source code or origin of an entity is accessible or obtainable.
-
D.
requiresSourceDisclosure
Indicates that performing or using something is contingent on revealing or making known the origin or source from which it was derived.
-
E.
requiresSourceCodeDisclosure
chosen
Indicates that one party is obligated to make the underlying source code available or visible to another party under specified conditions.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7af85c81909859e7247738a535 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.