Triple
T23234811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | p-adic analytic groups |
E581256
|
entity |
| Predicate | hasTangentObject |
P5510
|
FINISHED |
| Object | Lie algebra over Q_p |
—
|
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: Lie algebra over Q_p | Statement: [p-adic analytic groups, hasTangentObject, Lie algebra over Q_p]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTangentObject Context triple: [p-adic analytic groups, hasTangentObject, Lie algebra over Q_p]
-
A.
hasGradient
Indicates that one entity possesses or is characterized by a gradual change in value, intensity, or property across its extent or between two points.
-
B.
hasTorsion
Indicates that an object or structure possesses torsion, meaning it is subject to or characterized by twisting about an axis.
-
C.
hasTriangle
Indicates that an entity possesses, contains, or is associated with a triangle.
-
D.
hasObject
chosen
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
E.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
- 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.