Triple
T19327856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | p-adic numbers |
E483405
|
entity |
| Predicate | hasAbsoluteValue |
P72938
|
FINISHED |
| Object | p-adic absolute value |
—
|
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 absolute value | Statement: [p-adic numbers, hasAbsoluteValue, p-adic absolute value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbsoluteValue Context triple: [p-adic numbers, hasAbsoluteValue, p-adic absolute value]
-
A.
absoluteValue
chosen
Indicates the non-negative magnitude of a number, disregarding its sign.
-
B.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
C.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
D.
hasAbscissaOfAbsoluteConvergence
Indicates that a mathematical series or function is associated with a specific abscissa (a real boundary value on the real axis) beyond which its defining series converges absolutely.
-
E.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
- 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.