Triple
T1613491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satoshi Nakamoto |
E34660
|
entity |
| Predicate | activeDevelopmentPeriodEnd |
P12226
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Satoshi Nakamoto, activeDevelopmentPeriodEnd, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeDevelopmentPeriodEnd Context triple: [Satoshi Nakamoto, activeDevelopmentPeriodEnd, 2010]
-
A.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
B.
activeYearsEndTime
chosen
Indicates the point in time when an entity’s period of activity or operation comes to an end.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
developedAt
Indicates the place or location where something was created, built, or developed.
-
E.
mainDevelopmentPeriod
Indicates the primary time span during which the main development or formation of something took place.
- 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.