Triple
T27638590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Foundation |
E696528
|
entity |
| Predicate | hasFormerViceChairperson |
P178777
|
FINISHED |
| Object | Gavin Andresen |
—
|
NE NERFINISHED |
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: Gavin Andresen | Statement: [Bitcoin Foundation, hasFormerViceChairperson, Gavin Andresen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerViceChairperson Context triple: [Bitcoin Foundation, hasFormerViceChairperson, Gavin Andresen]
-
A.
hasFormerChairperson
Indicates that an entity previously held the role of chairperson of another entity, but no longer occupies that position.
-
B.
hasViceChair
Indicates that an entity holds the role or position of vice chair in relation to another entity (such as an organization, committee, or group).
-
C.
hasFormerChiefExecutive
Indicates that an entity previously held the role of chief executive for another entity.
-
D.
lastDeputyChairperson
Indicates that one entity served as the most recent deputy chairperson of another entity or organization.
-
E.
hasViceChairTitle
Indicates that an entity holds the position or bears the formal title of vice chair in relation to another entity or organization.
- 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_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 2:25 p.m.