Triple
T19242205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varius Rufus |
E481159
|
entity |
| Predicate | hasLostWork |
P32274
|
FINISHED |
| Object | epic poems |
—
|
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: epic poems | Statement: [Varius Rufus, hasLostWork, epic poems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLostWork Context triple: [Varius Rufus, hasLostWork, epic poems]
-
A.
hasLostWorks
chosen
Indicates that an entity has created works that are no longer extant, missing, or have not survived.
-
B.
hasWorkReleasedIn
Indicates that a creative work (such as a book, film, or album) was released or made publicly available in a particular time period or location.
-
C.
hasLostRelative
Indicates that one entity has experienced the death of a family member or close relative.
-
D.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
E.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf2353c819094a9a1af3a858715 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.