Triple
T19401758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Back |
E485340
|
entity |
| Predicate | roleInBitcoinEcosystem |
P3571
|
FINISHED |
| Object | early technical contributor |
—
|
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: early technical contributor | Statement: [Adam Back, roleInBitcoinEcosystem, early technical contributor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBitcoinEcosystem Context triple: [Adam Back, roleInBitcoinEcosystem, early technical contributor]
-
A.
roleInEcosystem
chosen
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
B.
roleInFinance
Indicates that an entity holds a specific function, responsibility, or position within a financial context, system, or transaction.
-
C.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
D.
roleInStellarFusion
Indicates the specific function or contribution an entity has within the processes that drive stellar nuclear fusion.
-
E.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62577454c81909d5bcd07e99b27e4 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.