Triple
T1613490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satoshi Nakamoto |
E34660
|
entity |
| Predicate | activeDevelopmentPeriodStart |
P7730
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Satoshi Nakamoto, activeDevelopmentPeriodStart, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeDevelopmentPeriodStart Context triple: [Satoshi Nakamoto, activeDevelopmentPeriodStart, 2007]
-
A.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
-
B.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developedAt
Indicates the place or location where something was created, built, or developed.
-
D.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
E.
activeFrom
chosen
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.