Triple
T35716956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dienstreizen van een thuisblijver |
E1032040
|
entity |
| Predicate | tijdperkVanPublicatie |
P3627
|
FINISHED |
| Object | 20e eeuw |
—
|
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: 20e eeuw | Statement: [Dienstreizen van een thuisblijver, tijdperkVanPublicatie, 20e eeuw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tijdperkVanPublicatie Context triple: [Dienstreizen van een thuisblijver, tijdperkVanPublicatie, 20e eeuw]
-
A.
epochAtPublication
Indicates the specific time or epoch at which the publication event occurs or is recorded.
-
B.
periodOfRelease
Indicates the time span or date range during which something (such as a work, product, or version) is officially released or made available.
-
C.
publicationPeriod
chosen
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
D.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
E.
republicationYear
Indicates the year in which a work is published again after its original publication.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.