Triple
T33579661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | idèle class group |
E860117
|
entity |
| Predicate | dualObject |
P31338
|
FINISHED |
| Object | Hecke characters |
—
|
NE NERFINISHED |
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: Hecke characters | Statement: [idèle class group, dualObject, Hecke characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dualObject Context triple: [idèle class group, dualObject, Hecke characters]
-
A.
dualPair
chosen
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
B.
dualUse
Indicates that something serves both civilian and military (or peaceful and non-peaceful) purposes simultaneously.
-
C.
designedObject
Indicates that one entity is the creator or designer of another entity as its intended product or outcome.
-
D.
dualisticContext
Indicates a relationship or situation in which two contrasting or opposing aspects, perspectives, or forces are simultaneously present and contextually relevant.
-
E.
hasDualSpace
Indicates that one mathematical space is the dual space consisting of all linear functionals defined on another space.
- 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.