Triple
T12597429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heun’s method |
E300767
|
entity |
| Predicate | isSingleStepMethod |
P28824
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heun’s method, isSingleStepMethod, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSingleStepMethod Context triple: [Heun’s method, isSingleStepMethod, true]
-
A.
isOneStepMethod
chosen
Indicates that a method or process completes the intended task in a single, indivisible step or operation.
-
B.
hasStep
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
C.
isFirstOrderMethod
Indicates that a method or procedure operates at the first order, typically using only first-order logic or first-order derivatives without involving higher-order constructs.
-
D.
usesMultiStepReturn
Indicates that an entity performs or supports a return process that occurs in multiple sequential steps rather than a single, direct action.
-
E.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.