Triple
T25677051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GF(p^m) |
E643835
|
entity |
| Predicate | subfieldsCorrespondTo |
P158981
|
FINISHED |
| Object | divisors of m |
—
|
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: divisors of m | Statement: [GF(p^m), subfieldsCorrespondTo, divisors of m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subfieldsCorrespondTo Context triple: [GF(p^m), subfieldsCorrespondTo, divisors of m]
-
A.
belongsToSubfield
Indicates that one field, topic, or area of study is a more specialized part within a broader academic or disciplinary field.
-
B.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
-
C.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
D.
subfamilyCorrespondence
Indicates a correspondence or mapping between subfamilies, specifying how one subfamily relates or aligns to another within a broader family structure.
-
E.
containsAsSubfield
Indicates that one field or data structure includes another field as a nested or component subfield within it.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3712cc8190b6e851960cc7c9e9 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:40 p.m.