Triple
T4581819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jutland Post |
E101871
|
entity |
| Predicate | publicationDateOfEvent |
P46931
|
FINISHED |
| Object | 30 September 2005 |
—
|
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: 30 September 2005 | Statement: [The Jutland Post, publicationDateOfEvent, 30 September 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationDateOfEvent Context triple: [The Jutland Post, publicationDateOfEvent, 30 September 2005]
-
A.
publishedAtEvent
chosen
Indicates that something (such as a work, announcement, or result) was formally released or made public in connection with a specific event.
-
B.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
C.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
D.
publishedEvent
Indicates that an entity has formally released or made an event publicly available or announced.
-
E.
datePresented
Indicates the date on which something (such as an item, work, or information) was formally presented or made known to an audience or recipient.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd590116e88190b8495b2a78cf3fb6 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.