Triple
T35105891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | manuscripts of Vox Clamantis |
E1013150
|
entity |
| Predicate | subjectWorkTitle |
P24259
|
FINISHED |
| Object | Vox Clamantis |
—
|
NE NERFINISHED |
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: Vox Clamantis | Statement: [manuscripts of Vox Clamantis, subjectWorkTitle, Vox Clamantis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectWorkTitle Context triple: [manuscripts of Vox Clamantis, subjectWorkTitle, Vox Clamantis]
-
A.
workTitle
chosen
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an entity.
-
B.
workTitleIn
Indicates that one entity is the title of a work (e.g., book, film, artwork) that appears within or is contained in another entity.
-
C.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
D.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
-
E.
workTitleWithOpus
Indicates that a work’s title is associated with a specific opus number designation.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:01 p.m.