Triple
T36840981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horatian corpus |
E910406
|
entity |
| Predicate | containsWorkWithTitle |
P3254
|
FINISHED |
| Object | Carmina |
—
|
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: Carmina | Statement: [Horatian corpus, containsWorkWithTitle, Carmina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWorkWithTitle Context triple: [Horatian corpus, containsWorkWithTitle, Carmina]
-
A.
workTitleContains
Indicates that the title of a work includes a specified substring or term.
-
B.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
C.
hasWorkTitleType
Indicates that an entity holds a specific category or type of work-related title (e.g., job title type or role classification).
-
D.
containsTitle
chosen
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
E.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
Created at: May 3, 2026, 4:13 p.m.