Triple
T15490322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger De Vlaeminck |
E378664
|
entity |
| Predicate | retirementDecade |
P7068
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Roger De Vlaeminck, retirementDecade, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementDecade Context triple: [Roger De Vlaeminck, retirementDecade, 1980s]
-
A.
retirementYear
Indicates the specific year in which an entity retires or is officially considered retired.
-
B.
retirementPeriod
Indicates the time span during which an entity is considered to be retired or in retirement status.
-
C.
decade
chosen
Indicates that the relationship or event is associated with, occurs within, or is characteristic of a specific ten-year time period.
-
D.
plannedRetirement
Indicates that an entity has scheduled or intends to end its active role or service at a specified future time.
-
E.
retired
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fac2af88190ac1d119e6b21dbe0 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:48 a.m.