Triple
T28793482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macrobius |
E727021
|
entity |
| Predicate | literaryFormOfSaturnalia |
P6480
|
FINISHED |
| Object | dialogue |
—
|
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: dialogue | Statement: [Macrobius, literaryFormOfSaturnalia, dialogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryFormOfSaturnalia Context triple: [Macrobius, literaryFormOfSaturnalia, dialogue]
-
A.
literaryMovementSatirized
Indicates that a literary movement is the target of satire or critical ridicule in a given work or by a given author.
-
B.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
C.
literaryScript
Indicates a relationship where an entity serves as the written text or script of a literary work, such as a play, film, or other narrative production.
-
D.
literaryThemeInvolvement
Indicates the involvement or presence of a particular literary theme within a work, passage, or character arc.
-
E.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 6:24 a.m.