Triple
T10389145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weil divisor |
E244844
|
entity |
| Predicate | hasCoefficientType |
P93927
|
FINISHED |
| Object | integer |
—
|
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: integer | Statement: [Weil divisor, hasCoefficientType, integer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoefficientType Context triple: [Weil divisor, hasCoefficientType, integer]
-
A.
hasCoefficientRing
Indicates that one mathematical structure (typically an algebra or module) is defined over, and takes its scalar values from, a specified ring that serves as its coefficient ring.
-
B.
coefficientProperty
Indicates a relationship where one entity serves as a coefficient or scalar factor that quantitatively modifies or characterizes another entity or property.
-
C.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
D.
hasTypeCode
Indicates that an entity is associated with a specific type classification represented by a code.
-
E.
firstCoefficientProperty
Indicates a property or characteristic specifically associated with the first coefficient in a mathematical or algebraic expression.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9b40dd8819080ac839487020a44 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:05 p.m.