Triple
T38626352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vila vid denna källa |
E937319
|
entity |
| Predicate | hasApproximateYearOfPublication |
P187456
|
FINISHED |
| Object | 1790 |
—
|
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: 1790 | Statement: [Vila vid denna källa, hasApproximateYearOfPublication, 1790]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateYearOfPublication Context triple: [Vila vid denna källa, hasApproximateYearOfPublication, 1790]
-
A.
textPublicationApproxYear
chosen
Indicates that a text was published around a specified year, with the year representing an approximate rather than exact publication date.
-
B.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
C.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
D.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
E.
lastPublicationYear
Indicates the year in which an entity’s most recent publication was released.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 3, 2026, 4:32 p.m.