Triple
T7899053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hal Finney |
E183402
|
entity |
| Predicate | wasEarlyContributorTo |
P2809
|
FINISHED |
| Object | Bitcoin codebase |
—
|
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: Bitcoin codebase | Statement: [Hal Finney, wasEarlyContributorTo, Bitcoin codebase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEarlyContributorTo Context triple: [Hal Finney, wasEarlyContributorTo, Bitcoin codebase]
-
A.
firstContributor
Indicates that the subject is the earliest or initial contributor to the object within a given context or project.
-
B.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
C.
pioneerOf
chosen
Indicates that an entity was among the first to develop, introduce, or significantly advance another entity, concept, or practice.
-
D.
wasEarlyAdopterOf
Indicates that an entity adopted, used, or supported something significantly earlier than most others.
-
E.
wasFoundedBy
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a2ae5048190a6824d34b582c366 |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.