Triple
T35716954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dienstreizen van een thuisblijver |
E1032040
|
entity |
| Predicate | publicatievorm |
P218
|
FINISHED |
| Object | proza |
—
|
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: proza | Statement: [Dienstreizen van een thuisblijver, publicatievorm, proza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicatievorm Context triple: [Dienstreizen van een thuisblijver, publicatievorm, proza]
-
A.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
B.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
C.
publicationMethod
Indicates the means or process by which something is published, such as the format, channel, or medium used to make it publicly available.
-
D.
publish
Indicates making content publicly available or formally issuing it, typically through a medium such as print or digital platforms.
-
E.
publicationOfWork
Indicates that a particular work has been formally made public, typically through printing, distribution, or release by a publisher or similar entity.
- 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_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:05 p.m.