Triple
T2364335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computer algebra system |
E47345
|
entity |
| Predicate | typicalInput |
P12230
|
FINISHED |
| Object | mathematical expressions |
—
|
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: mathematical expressions | Statement: [Computer algebra system, typicalInput, mathematical expressions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInput Context triple: [Computer algebra system, typicalInput, mathematical expressions]
-
A.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
B.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
D.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
E.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc7486cb48190acef1891cc87bdb1 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.