Triple
T34209935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elagabal |
E877625
|
entity |
| Predicate | timeOfRomanPromotion |
P193898
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [Elagabal, timeOfRomanPromotion, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfRomanPromotion Context triple: [Elagabal, timeOfRomanPromotion, 3rd century]
-
A.
startTimeInRomanCalendar
Indicates the point in time when an event or interval begins, expressed using the Roman calendar system.
-
B.
underRomanRuleBecame
Indicates that an entity, once under Roman political or administrative control, subsequently transformed into or was reconstituted as another specified entity.
-
C.
yearInRomanHistory
Indicates that a specific year is notable or relevant within the context of Roman history.
-
D.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
E.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
- F. None of above. chosen
Provenance (4 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
| PDg | Predicate description generation | batch_69fd592cc56081908ce456114d407616 |
completed | May 8, 2026, 3:31 a.m. |
Created at: May 1, 2026, 1:55 a.m.