Triple
T33579713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartier divisor |
E860118
|
entity |
| Predicate | mayNotCoincideWith |
P53790
|
FINISHED |
| Object | Weil divisor on singular variety |
—
|
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: Weil divisor on singular variety | Statement: [Cartier divisor, mayNotCoincideWith, Weil divisor on singular variety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayNotCoincideWith Context triple: [Cartier divisor, mayNotCoincideWith, Weil divisor on singular variety]
-
A.
mayOverlapIn
Indicates that two entities are allowed or able to occupy overlapping positions, extents, or intervals in space, time, or another dimension.
-
B.
notCoterminousWith
Indicates that two entities do not share the same boundaries in space, time, or extent and therefore are not exactly coincident.
-
C.
mayDifferFrom
chosen
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
-
D.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
E.
mayNotFit
Indicates that one entity is unlikely or not expected to be suitable in size, capacity, or compatibility to be placed into, combined with, or used within another entity or context.
- 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_69f6f76f757081909165948fdcb254c7 |
completed | May 3, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.