Triple
T7899187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segregated Witness |
E183405
|
entity |
| Predicate | firstActivatedOn |
P20170
|
FINISHED |
| Object | Bitcoin mainnet |
—
|
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 mainnet | Statement: [Segregated Witness, firstActivatedOn, Bitcoin mainnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstActivatedOn Context triple: [Segregated Witness, firstActivatedOn, Bitcoin mainnet]
-
A.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
B.
firstOpenedAt
Indicates the date and time at which something was initially opened for the first time.
-
C.
firstInvocationDate
Indicates the date on which the entity was first invoked, used, or called for the first time.
-
D.
firstUsedOn
chosen
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
E.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
- 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.