Triple
T18265913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knuth license |
E437482
|
entity |
| Predicate | useCondition |
P123750
|
FINISHED |
| Object | programs may be used freely |
—
|
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: programs may be used freely | Statement: [Knuth license, useCondition, programs may be used freely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useCondition Context triple: [Knuth license, useCondition, programs may be used freely]
-
A.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
C.
variableCondition
Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
-
D.
supportsCondition
Indicates that one entity helps maintain, enable, or is compatible with a particular condition or state in another entity.
-
E.
usedCondition
chosen
Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
- 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.