Triple
T23234812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | p-adic analytic groups |
E581256
|
entity |
| Predicate | localCoordinateModel |
P2054
|
FINISHED |
| Object | open subsets of Q_p^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: open subsets of Q_p^n | Statement: [p-adic analytic groups, localCoordinateModel, open subsets of Q_p^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localCoordinateModel Context triple: [p-adic analytic groups, localCoordinateModel, open subsets of Q_p^n]
-
A.
coordinateOf
Indicates that one entity specifies the spatial or positional coordinates associated with another entity.
-
B.
usesCoordinateRepresentation
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
C.
modelingLocation
Indicates the place or setting where the modeling activity or process occurs.
-
D.
coordinatesMode
Indicates that one entity specifies or controls the coordinate system or reference frame used to interpret the spatial data of another entity.
-
E.
coordinateSystem
chosen
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e8c7548190b53434eeb2620a6e |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.