Triple
T18266267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | noweb |
E437491
|
entity |
| Predicate | notangleFunction |
P131101
|
FINISHED |
| Object | extracts source code from literate file |
—
|
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: extracts source code from literate file | Statement: [noweb, notangleFunction, extracts source code from literate file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notangleFunction Context triple: [noweb, notangleFunction, extracts source code from literate file]
-
A.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
B.
notCrossing
Indicates that two entities do not intersect, overlap, or pass through each other in space or along their paths.
-
C.
notShapedBy
Indicates that one entity does not influence, determine, or define the form, structure, or characteristics of another entity.
-
D.
notAlignedWith
Indicates that one entity’s position, orientation, or viewpoint does not correspond or agree with that of another entity.
-
E.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.