Triple
T11862151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM curve |
E282184
|
entity |
| Predicate | hasAxisVariable |
P38220
|
FINISHED |
| Object | interest rate on the vertical axis |
—
|
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: interest rate on the vertical axis | Statement: [LM curve, hasAxisVariable, interest rate on the vertical axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAxisVariable Context triple: [LM curve, hasAxisVariable, interest rate on the vertical axis]
-
A.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
-
B.
hasAxisConfiguration
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by another entity.
-
C.
hasIndependentVariable
Indicates that one entity functions as the independent variable that influences or determines another entity in a relationship or experiment.
-
D.
hasIntermediateAxisLength
Indicates that an entity is associated with a specific value representing the length of its intermediate (middle-sized) axis.
-
E.
hasVariable
chosen
Indicates that one entity includes, defines, or is associated with a particular variable.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.