Triple
T9955624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melesias |
E195438
|
entity |
| Predicate | workAuthoredIn |
P91351
|
FINISHED |
| Object | 4th century BCE |
—
|
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: 4th century BCE | Statement: [Melesias, workAuthoredIn, 4th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAuthoredIn Context triple: [Melesias, workAuthoredIn, 4th century BCE]
-
A.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
-
B.
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.
-
C.
workOfAuthorWho
Indicates that one entity is a work (such as a book, article, or artwork) created by another entity who is its author.
-
D.
workAuthorIs
Indicates that a specific person or entity is the author or creator of a particular work.
-
E.
workWriterOfWorkAppearedIn
Indicates that a work is written by an author whose work appeared in a particular publication or context.
- F. None of above. chosen
Provenance (4 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb69631d08190ab2b1d1c22d46da7 |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:46 p.m.