Triple
T7899188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segregated Witness |
E183405
|
entity |
| Predicate | firstSignaledBy |
P79657
|
FINISHED |
| Object | Bitcoin miners |
—
|
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 miners | Statement: [Segregated Witness, firstSignaledBy, Bitcoin miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSignaledBy Context triple: [Segregated Witness, firstSignaledBy, Bitcoin miners]
-
A.
wasFirstHeldBy
Indicates that an event or activity was initially hosted, organized, or conducted by a particular entity.
-
B.
firstClaimedBy
Indicates that the referenced entity was the first to assert ownership, discovery, or authorship of another entity.
-
C.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
-
D.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
-
E.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
- 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_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. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:01 p.m.