Triple
T26622572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Newell |
E668238
|
entity |
| Predicate | usedToolOrMethod |
P91992
|
FINISHED |
| Object | splines in geometric modeling |
—
|
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: splines in geometric modeling | Statement: [Martin Newell, usedToolOrMethod, splines in geometric modeling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToolOrMethod Context triple: [Martin Newell, usedToolOrMethod, splines in geometric modeling]
-
A.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
B.
usesToolFor
chosen
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
C.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
D.
theoryUsed
Indicates that one entity applies, relies on, or is based upon a particular theory in its reasoning, explanation, or methodology.
-
E.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 2:21 a.m.