Triple
T28793472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macrobius |
E727021
|
entity |
| Predicate | discussesInWorks |
P80280
|
FINISHED |
| Object | Roman religion |
—
|
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: Roman religion | Statement: [Macrobius, discussesInWorks, Roman religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discussesInWorks Context triple: [Macrobius, discussesInWorks, Roman religion]
-
A.
discussedInWorkOf
chosen
Indicates that a subject is examined, treated, or talked about within a particular work or publication.
-
B.
notableWorkDiscussed
Indicates that a particular work (such as a book, film, or artwork) is the subject of discussion, analysis, or commentary in relation to another entity.
-
C.
hasWorksAbout
Indicates that one entity (such as a creator, collection, or source) includes or is associated with works whose subject or focus is another entity.
-
D.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
E.
commentaryWorkFor
Indicates that one entity performs commentary or analysis work on behalf of, or under employment/contract with, another entity.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:24 a.m.