Triple
T14334246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | manuscripts of Isaac Newton |
E355429
|
entity |
| Predicate | containsWorkOn |
P44667
|
FINISHED |
| Object | calculus |
—
|
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: calculus | Statement: [manuscripts of Isaac Newton, containsWorkOn, calculus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWorkOn Context triple: [manuscripts of Isaac Newton, containsWorkOn, calculus]
-
A.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
B.
includedWorkOn
chosen
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
C.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
D.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
E.
hasWorkProduct
Indicates that one entity produces, creates, or is responsible for a particular work product or output associated with it.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c20d2148190bb534bef338e871d |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.