Triple
T27638545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hal Finney |
E696527
|
entity |
| Predicate | posted |
P38037
|
FINISHED |
| Object | "Running bitcoin" tweet |
—
|
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: "Running bitcoin" tweet | Statement: [Hal Finney, posted, "Running bitcoin" tweet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posted Context triple: [Hal Finney, posted, "Running bitcoin" tweet]
-
A.
postedIn
Indicates that a piece of content or message was submitted or shared within a particular forum, group, channel, or location.
-
B.
createdPost
chosen
Indicates that an entity authored or produced a specific post.
-
C.
laterPosting
Indicates that one posting, message, or publication occurs at a later time than another in a temporal sequence.
-
D.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
E.
postPosition
Indicates that one entity is located behind or to the rear of another entity in space or sequence.
- 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:25 p.m.