Triple
T265531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin |
E5715
|
entity |
| Predicate | isPermissionless |
P8897
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bitcoin, isPermissionless, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPermissionless Context triple: [Bitcoin, isPermissionless, true]
-
A.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
B.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
C.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
D.
minedBy
Indicates that a resource, material, or location is extracted or obtained through mining activities performed by a specified agent or entity.
-
E.
doesNotParticipateIn
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c8ae480819094f6d1bb0a6d2eb2 |
completed | Feb. 28, 2026, 3:10 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.