Triple
T6236538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplace transform |
E139491
|
entity |
| Predicate | variableName |
P50849
|
FINISHED |
| Object | t |
—
|
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: t | Statement: [Laplace transform, variableName, t]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variableName Context triple: [Laplace transform, variableName, t]
-
A.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
B.
constantName
Indicates that an entity has a specific, fixed identifier or label used as a constant within a system or context.
-
C.
usesVAR
chosen
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
-
D.
reserveName
Indicates that an entity secures or sets aside a specific name so that it cannot be used by others.
-
E.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
- 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.