Triple
T34302557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | forward-backward algorithm |
E880218
|
entity |
| Predicate | forwardVariableName |
P101093
|
FINISHED |
| Object | alpha |
—
|
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: alpha | Statement: [forward-backward algorithm, forwardVariableName, alpha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forwardVariableName Context triple: [forward-backward algorithm, forwardVariableName, alpha]
-
A.
formalVariable
Indicates that an entity functions as a formal variable, typically serving as a placeholder or bound symbol within a formal expression, statement, or system.
-
B.
hasVariableName
Indicates that an entity (such as a variable or symbol) is associated with a specific variable name.
-
C.
variableUsuallyDenotedBy
chosen
Indicates that a given variable is most commonly represented or written using a particular symbol or notation.
-
D.
dstVariantName
Indicates that an entity has a specific variant name used or assigned as the destination in a mapping, transformation, or versioning context.
-
E.
discoveredAsVariableBy
Indicates that one entity was identified, recognized, or introduced as a variable by another entity (such as a person, process, or system).
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.