Triple
T27638904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SegWit2x |
E696535
|
entity |
| Predicate | hadImplementation |
P22535
|
FINISHED |
| Object | BTC1 software 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: BTC1 software client | Statement: [SegWit2x, hadImplementation, BTC1 software client]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadImplementation Context triple: [SegWit2x, hadImplementation, BTC1 software client]
-
A.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
B.
hasImplementationDetail
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
-
C.
implementedOn
chosen
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
D.
aimedToImplement
Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
-
E.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
- 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_69f6318fec0c8190971b4fc1a7df10d3 |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:25 p.m.