Triple
T21709536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ianuarius |
E535863
|
entity |
| Predicate | roleInRomanReligion |
P118406
|
FINISHED |
| Object | month sacred to Janus |
—
|
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: month sacred to Janus | Statement: [Ianuarius, roleInRomanReligion, month sacred to Janus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRomanReligion Context triple: [Ianuarius, roleInRomanReligion, month sacred to Janus]
-
A.
roleOfReferencedDeity
chosen
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
B.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
C.
religionInRomanPeriod
Indicates that an entity’s religious affiliation, practice, or status is specified as it existed during the Roman period.
-
D.
partOfPantheon
Indicates that an entity is a member or constituent deity of a particular pantheon or religious tradition.
-
E.
pantheonIncludesCultOf
Indicates that a particular pantheon encompasses or contains a specific cult within its religious structure or tradition.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5321d34819091f3cd03f7b407c0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.