Triple
T33579692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartier divisor |
E860118
|
entity |
| Predicate | hasLocalEquation |
P70766
|
FINISHED |
| Object | nonzero rational function |
—
|
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: nonzero rational function | Statement: [Cartier divisor, hasLocalEquation, nonzero rational function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalEquation Context triple: [Cartier divisor, hasLocalEquation, nonzero rational function]
-
A.
hasEquationForm
Indicates that one entity is expressed or represented in the form of a specific equation.
-
B.
hasLocalExpression
chosen
Indicates that something has a specific form, representation, or manifestation that is valid or defined only within a particular local context or region.
-
C.
hasEquationSide
Indicates a relationship where a particular expression or term belongs to a specific side (e.g., left or right) of an equation.
-
D.
hasEquationOfMotion
Indicates that one entity specifies or is associated with the equation of motion governing the dynamical behavior of another entity.
-
E.
hasLocalModel
Indicates that one entity possesses or uses a model that is stored or executed locally rather than accessed remotely.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 1, 2026, 1:40 a.m.