Triple
T32515980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | secp256k1 |
E831062
|
entity |
| Predicate | basePointSymbol |
P91203
|
FINISHED |
| Object | G |
—
|
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: G | Statement: [secp256k1, basePointSymbol, G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basePointSymbol Context triple: [secp256k1, basePointSymbol, G]
-
A.
centralPointSymbolizes
Indicates that a central point stands for, represents, or embodies a particular concept, value, or meaning within a given context.
-
B.
pointsSymbolize
Indicates that specific points are used to represent or stand for particular meanings, concepts, or values.
-
C.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
D.
mapSymbolStandard
Indicates that a map symbol conforms to, or is defined according to, a particular cartographic standard or specification.
-
E.
usesBasePoint
chosen
Indicates that one entity performs an operation or defines a structure by referencing or relying on a specific base point.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4a2e4cc81909158364159fac689 |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.