Triple
T32082367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter Tonans |
E819333
|
entity |
| Predicate | cultPatron |
P165270
|
FINISHED |
| Object | Augustus |
—
|
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: Augustus | Statement: [Jupiter Tonans, cultPatron, Augustus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultPatron Context triple: [Jupiter Tonans, cultPatron, Augustus]
-
A.
culturalPatronage
Indicates the support, promotion, or sponsorship of cultural activities, institutions, or creators by an individual, group, or organization.
-
B.
traditionalPatron
Indicates a relationship where one entity serves as a customary or historically established patron or supporter of another.
-
C.
laterPatron
Indicates that one entity serves as a patron of another at a later time than some reference patronage relationship.
-
D.
patron of
chosen
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
-
E.
coPatron
Indicates a relationship where two or more entities share joint responsibility or role as patrons supporting the same person, group, or endeavor.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b580c3e481909f45d1716cde89ad |
completed | May 3, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:24 a.m.