Triple
T15973932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Olympic Games: Being a Short History of the Olympic Movement from 1896 to 1906 |
E387392
|
entity |
| Predicate | documentedPeriodStart |
P88712
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [The Olympic Games: Being a Short History of the Olympic Movement from 1896 to 1906, documentedPeriodStart, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedPeriodStart Context triple: [The Olympic Games: Being a Short History of the Olympic Movement from 1896 to 1906, documentedPeriodStart, 1896]
-
A.
recordedInPeriodStart
chosen
Indicates that an event or record began or was first documented at the start of a specified time period.
-
B.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
C.
narratedPeriodStart
Indicates the point in time at which the narrated or described period begins.
-
D.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
E.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.