Triple
T33578791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frobenius endomorphism |
E860096
|
entity |
| Predicate | hasActionOn |
P9769
|
FINISHED |
| Object | cohomology groups of varieties over finite fields |
—
|
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: cohomology groups of varieties over finite fields | Statement: [Frobenius endomorphism, hasActionOn, cohomology groups of varieties over finite fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActionOn Context triple: [Frobenius endomorphism, hasActionOn, cohomology groups of varieties over finite fields]
-
A.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
B.
hasActs
Indicates that an entity is associated with one or more actions, performances, or deeds it carries out or is responsible for.
-
C.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
D.
hasOwnerAction
Indicates that an owner performs, initiates, or is responsible for a specific action related to the owned entity.
-
E.
hasActionType
Indicates that an action or event is classified as belonging to a specific type or category of actions.
- 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_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:40 a.m.