Triple
T33579725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartier divisor |
E860118
|
entity |
| Predicate | hasPoleLocus |
P198582
|
FINISHED |
| Object | subscheme defined by poles of local equations |
—
|
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: subscheme defined by poles of local equations | Statement: [Cartier divisor, hasPoleLocus, subscheme defined by poles of local equations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoleLocus Context triple: [Cartier divisor, hasPoleLocus, subscheme defined by poles of local equations]
-
A.
hasPoleAt
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
-
B.
hasOrderOfPoleAtLatticePoints
Indicates that a function has poles of specified orders at each point of a given lattice in its domain.
-
C.
hasPolarEquation
Indicates that an entity is associated with, or can be represented by, a specific equation expressed in polar coordinates.
-
D.
orderOfPoleAt
Indicates the location or index at which a function has a pole of a specified order.
-
E.
hasZeroLocus
Indicates that a mathematical object (such as a function or section) is associated with the set of points where it evaluates to zero.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:40 a.m.