Triple
T27638898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SegWit2x |
E696535
|
entity |
| Predicate | intendedActivationDate |
P26282
|
FINISHED |
| Object | 2017-11-16 |
—
|
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: 2017-11-16 | Statement: [SegWit2x, intendedActivationDate, 2017-11-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedActivationDate Context triple: [SegWit2x, intendedActivationDate, 2017-11-16]
-
A.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
B.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
C.
appliedDate
Indicates the date on which an application or request was submitted or made.
-
D.
implementedProgramStartDate
Indicates the date on which a particular program was put into effect or began operating in practice.
-
E.
plannedAt
chosen
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
- 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_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 2:25 p.m.