Triple
T24806718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korn inequality |
E620674
|
entity |
| Predicate | KornConstantDependsOn |
P157729
|
FINISHED |
| Object | type of boundary conditions |
—
|
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: type of boundary conditions | Statement: [Korn inequality, KornConstantDependsOn, type of boundary conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KornConstantDependsOn Context triple: [Korn inequality, KornConstantDependsOn, type of boundary conditions]
-
A.
KornConstantDependsOn
chosen
Indicates that a Korn constant is functionally dependent on, or determined by, another variable, parameter, or condition.
-
B.
kernelDependsOn
Indicates that one kernel or core software component requires another kernel or component to be present or available in order to function correctly.
-
C.
includesConstant
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
D.
conceptuallyDependsOn
Indicates that one entity’s definition, validity, or understanding relies on or is grounded in the concepts provided by another entity.
-
E.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:50 a.m.