Triple
T32516689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weierstrass form |
E831077
|
entity |
| Predicate | hasAffineChart |
P174540
|
FINISHED |
| Object | equation in variables x and y |
—
|
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: equation in variables x and y | Statement: [Weierstrass form, hasAffineChart, equation in variables x and y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAffineChart Context triple: [Weierstrass form, hasAffineChart, equation in variables x and y]
-
A.
hasChart
Indicates that one entity is associated with, represented by, or documented through a chart belonging to or describing it.
-
B.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
-
C.
usesChartsOf
Indicates that one entity employs or relies on the charts, diagrams, or graphical representations provided by another entity.
-
D.
hasChartStatus
Indicates that an entity is associated with a particular chart-related state or condition (e.g., its current status within a chart or dashboard).
-
E.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
- F. None of above. chosen
Provenance (4 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4a2e4cc81909158364159fac689 |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1 a.m.