Triple
T6236543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplace transform |
E139491
|
entity |
| Predicate | hasInverse |
P21517
|
FINISHED |
| Object | inverse Laplace transform |
—
|
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: inverse Laplace transform | Statement: [Laplace transform, hasInverse, inverse Laplace transform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInverse Context triple: [Laplace transform, hasInverse, inverse Laplace transform]
-
A.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
B.
isInverseOf
chosen
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
hasArc
Indicates that there is a directed connection or edge from one entity to another, often representing a link in a graph or network.
-
E.
hasInversionCapability
Indicates that an entity possesses the ability to reverse or invert another entity, state, or process.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063021258819093a9237041816638 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.