Triple
T19562337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibullus |
E489484
|
entity |
| Predicate | hasPartInCorpus |
P67055
|
FINISHED |
| Object | poems addressed to Delia |
—
|
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: poems addressed to Delia | Statement: [Tibullus, hasPartInCorpus, poems addressed to Delia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInCorpus Context triple: [Tibullus, hasPartInCorpus, poems addressed to Delia]
-
A.
hasPartOfCorpus
chosen
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
B.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
C.
isPartOfBodyOfWork
Indicates that one creative work is a component, segment, or installment within a larger overarching body of related work.
-
D.
numberInCorpus
Indicates the numerical count or frequency with which a given item appears within a specified corpus.
-
E.
hasPartInCreativeOutput
Indicates that an entity contributed a component, role, or involvement to the creation or production of a particular creative work.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f74fdb08190852461b5d5c954ac |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.