Triple
T19327851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | p-adic numbers |
E483405
|
entity |
| Predicate | hasSubring |
P5797
|
FINISHED |
| Object | p-adic integers |
—
|
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: p-adic integers | Statement: [p-adic numbers, hasSubring, p-adic integers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubring Context triple: [p-adic numbers, hasSubring, p-adic integers]
-
A.
isSubquotientOf
Indicates that one object can be obtained from another by first taking a subobject and then forming a quotient of that subobject.
-
B.
hasSubgroupIsomorphicTo
Indicates that one group contains a subgroup that is structurally identical (isomorphic) to another specified group.
-
C.
isClosedSubgroupOf
Indicates that one group is a subgroup of another and is closed in the topological sense within that larger group.
-
D.
hasSubset
chosen
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
-
E.
isMaximalSubgroupOf
Indicates that one group is a proper subgroup of another that is not contained in any larger proper subgroup of that group.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6163f32f48190be17cccf4e537372 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:33 p.m.