Triple
T12597434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heun’s method |
E300767
|
entity |
| Predicate | implementationComplexity |
P28756
|
FINISHED |
| Object | simple |
—
|
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: simple | Statement: [Heun’s method, implementationComplexity, simple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationComplexity Context triple: [Heun’s method, implementationComplexity, simple]
-
A.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
B.
parsingComplexity
Indicates the level of difficulty or computational effort required to parse or analyze a given input or structure.
-
C.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
D.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
-
E.
implementationType
Indicates the specific manner or approach by which something is implemented or realized in practice.
- 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.