Triple
T27638949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin testnet |
E696536
|
entity |
| Predicate | addressPrefixP2PKH |
P163933
|
FINISHED |
| Object | m or 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: m or n | Statement: [Bitcoin testnet, addressPrefixP2PKH, m or n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressPrefixP2PKH Context triple: [Bitcoin testnet, addressPrefixP2PKH, m or n]
-
A.
addressPrefixMainnet
Indicates that an address has the prefix format used for the main (primary/production) network.
-
B.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
C.
shieldedAddressPrefix
Indicates that an address begins with a specific prefix used for shielded or privacy-protecting transactions.
-
D.
addressExamplePrefix
Indicates that an address example is introduced or categorized by a specific prefix string used to distinguish or group it.
-
E.
bech32HumanReadablePart
Indicates that one entity specifies the human-readable prefix portion of a Bech32-encoded string associated with another entity.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 2:25 p.m.