Triple
T32030658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calderón problem in inverse conductivity |
E817947
|
entity |
| Predicate | unknown |
P148132
|
FINISHED |
| Object | conductivity γ(x) |
—
|
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: conductivity γ(x) | Statement: [Calderón problem in inverse conductivity, unknown, conductivity γ(x)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unknown Context triple: [Calderón problem in inverse conductivity, unknown, conductivity γ(x)]
-
A.
unknownFor
chosen
Indicates that some information, value, or property about one entity is not known or not determined with respect to another entity.
-
B.
известенС
Indicates that one entity is known or recognized by another entity.
-
C.
never
Indicates that the specified relationship or action does not occur at any time or under any circumstances.
-
D.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
E.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b494f66c8190ada271cdb0a21195 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:18 a.m.