Triple
T20360589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ventidius |
E496765
|
entity |
| Predicate | workDateWritten |
P19743
|
FINISHED |
| Object | circa 1606 |
—
|
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: circa 1606 | Statement: [Ventidius, workDateWritten, circa 1606]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workDateWritten Context triple: [Ventidius, workDateWritten, circa 1606]
-
A.
hasDateWritten
chosen
Indicates that something is associated with the specific date on which it was written.
-
B.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
C.
writtenAtEvent
Indicates that a writing or inscription activity occurred during or in connection with a specific event.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678584294819093788ccf2fb8e588 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.