Triple
T19327860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | p-adic numbers |
E483405
|
entity |
| Predicate | isCompleteWithRespectTo |
P135623
|
FINISHED |
| Object | p-adic metric |
—
|
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 metric | Statement: [p-adic numbers, isCompleteWithRespectTo, p-adic metric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCompleteWithRespectTo Context triple: [p-adic numbers, isCompleteWithRespectTo, p-adic metric]
-
A.
isCompleteFor
Indicates that one entity fully satisfies or finishes the requirements, scope, or intended purpose of another entity.
-
B.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
C.
isCompleteOn
Indicates that an activity, task, or process has been fully finished or achieved by a specific point in time or on a specific date.
-
D.
isIncompletenessSubjectTo
Indicates that an incompleteness, deficiency, or lack in something is governed, constrained, or determined by a particular condition, rule, or authority.
-
E.
hasCompleted
Indicates that an entity has finished or successfully carried out a specified task, process, or activity.
- 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_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. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:33 p.m.