Triple
T20544256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bikecentennial |
E504423
|
entity |
| Predicate | mainEventDate |
P140492
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Bikecentennial, mainEventDate, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventDate Context triple: [Bikecentennial, mainEventDate, 1976]
-
A.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
majorFestivalDate
Indicates the calendar date on which a major festival or significant celebratory event takes place.
-
D.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
E.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a2957c308190aab81127f82f8aa6 |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.