Triple
T18265916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knuth license |
E437482
|
entity |
| Predicate | nameRestriction |
P76927
|
FINISHED |
| Object | original program name reserved for Knuth’s own versions |
—
|
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: original program name reserved for Knuth’s own versions | Statement: [Knuth license, nameRestriction, original program name reserved for Knuth’s own versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameRestriction Context triple: [Knuth license, nameRestriction, original program name reserved for Knuth’s own versions]
-
A.
nameRequirement
chosen
Indicates that there is a specified condition or constraint that a name must satisfy.
-
B.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
C.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
D.
nameUsedToAvoid
Indicates that one entity uses a particular name or designation in order to avoid another entity or an unwanted situation involving that entity.
-
E.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
- 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.