Triple
T34472160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drinfeld modules |
E884935
|
entity |
| Predicate | hasAnalogueOf |
P138778
|
FINISHED |
| Object | Mordell–Weil theorem |
E641515
|
NE 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: Mordell–Weil theorem | Statement: [Drinfeld modules, hasAnalogueOf, Mordell–Weil theorem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnalogueOf Context triple: [Drinfeld modules, hasAnalogueOf, Mordell–Weil theorem]
-
A.
hasAnalog
chosen
Indicates that one entity corresponds to or functions similarly to another entity in a comparable context or role.
-
B.
hasLocalAnalogue
Indicates that one entity has a corresponding or comparable counterpart in a local or context-specific setting.
-
C.
usedAsAnalogFor
Indicates that one entity is employed as a comparison or illustrative counterpart to help explain, represent, or understand another entity.
-
D.
hasSmallerCounterpart
Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
-
E.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
- F. None of above.
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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a372131c44c819081c38649593d53c6 |
completed | June 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 2:01 a.m.