Triple
T16585836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsinore Castle |
E402953
|
entity |
| Predicate | workFirstPublished |
P47750
|
FINISHED |
| Object | early 17th century |
—
|
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: early 17th century | Statement: [Elsinore Castle, workFirstPublished, early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFirstPublished Context triple: [Elsinore Castle, workFirstPublished, early 17th century]
-
A.
firstDraftPublishedIn
Indicates that the first draft of a work was published or made publicly available in a specified venue, medium, or publication.
-
B.
firstPublicationIn
chosen
Indicates the initial venue, medium, or context in which a work was first published.
-
C.
workFirstPublishedAsPlay
Indicates that the work was originally first published in the form of a play.
-
D.
firstPublicationUnderName
Indicates that an entity’s first publication occurred using a specified name (e.g., pseudonym, pen name, or new legal name).
-
E.
workPublishedBy
Indicates that a work (such as a book, article, or other creation) has been issued or made publicly available by a particular publisher or publishing 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599cbc448190bc80eef4ad58eb41 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.