Triple
T1613598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis Block |
E34662
|
entity |
| Predicate | softwareClient |
P10387
|
FINISHED |
| Object | original Bitcoin client |
—
|
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: original Bitcoin client | Statement: [Genesis Block, softwareClient, original Bitcoin client]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareClient Context triple: [Genesis Block, softwareClient, original Bitcoin client]
-
A.
usesSoftware
chosen
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
B.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
-
C.
softwareModel
Indicates that one entity serves as a software-based representation or abstraction (a model) of another entity or system.
-
D.
successorSoftware
Indicates that one software product directly follows and replaces another as its newer version or update.
-
E.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.