Triple
T27638587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Foundation |
E696528
|
entity |
| Predicate | hasFormerExecutiveDirector |
P10190
|
FINISHED |
| Object | Jon Matonis |
—
|
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: Jon Matonis | Statement: [Bitcoin Foundation, hasFormerExecutiveDirector, Jon Matonis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerExecutiveDirector Context triple: [Bitcoin Foundation, hasFormerExecutiveDirector, Jon Matonis]
-
A.
hasFormerChairperson
Indicates that an entity previously held the role of chairperson of another entity, but no longer occupies that position.
-
B.
hasFormerChiefExecutive
Indicates that an entity previously held the role of chief executive for another entity.
-
C.
formerDirector
chosen
Indicates that one entity previously held the position of director of the other entity but no longer does.
-
D.
hasFormerFounder
Indicates that an entity was previously a founder of another entity but no longer holds that founder role or status.
-
E.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 2:25 p.m.