Triple
T36513198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artin L-functions |
E899965
|
entity |
| Predicate | areAttachedTo |
P10139
|
FINISHED |
| Object | Galois representations |
—
|
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: Galois representations | Statement: [Artin L-functions, areAttachedTo, Galois representations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areAttachedTo Context triple: [Artin L-functions, areAttachedTo, Galois representations]
-
A.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
attachesUsing
Indicates that one entity becomes fastened, connected, or secured to another by means of a specified tool, mechanism, or method.
-
C.
tiedTo
Indicates that one entity is physically or figuratively fastened, bound, or otherwise constrained in connection to another entity.
-
D.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.