Triple
T27025705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tate Conjecture |
E680776
|
entity |
| Predicate | groupActing |
P164307
|
FINISHED |
| Object | absolute Galois group of the finite field |
—
|
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: absolute Galois group of the finite field | Statement: [Tate Conjecture, groupActing, absolute Galois group of the finite field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupActing Context triple: [Tate Conjecture, groupActing, absolute Galois group of the finite field]
-
A.
groupTogether
Indicates that multiple entities are treated or arranged as a single collective unit or set.
-
B.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
C.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
D.
studentGroup
Indicates that an entity is a group or collective of students associated together for a common purpose or activity.
-
E.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 7:11 a.m.