Triple
T7420252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noether field |
E171227
|
entity |
| Predicate | isFixedFieldOf |
P76857
|
FINISHED |
| Object | group action of G on K(x_1,…,x_n) |
—
|
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: group action of G on K(x_1,…,x_n) | Statement: [Noether field, isFixedFieldOf, group action of G on K(x_1,…,x_n)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFixedFieldOf Context triple: [Noether field, isFixedFieldOf, group action of G on K(x_1,…,x_n)]
-
A.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
B.
inSameFieldAs
Indicates that two entities work, study, or specialize within the same professional or academic field.
-
C.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
D.
definesField
Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
-
E.
fromField
Indicates that something originates in, is sourced from, or is associated with a particular field or domain.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ea61248190886e8e55b42ba5f1 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.