Triple
T31079404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iordanes |
E792058
|
entity |
| Predicate | Romana_subject |
P28173
|
FINISHED |
| Object | universal history from Creation to his own time |
—
|
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: universal history from Creation to his own time | Statement: [Iordanes, Romana_subject, universal history from Creation to his own time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Romana_subject Context triple: [Iordanes, Romana_subject, universal history from Creation to his own time]
-
A.
Chronica_subject
chosen
Indicates that an entity serves as the subject or main focus of a chronicle, record, or historical account.
-
B.
rom
Indicates a romantic relationship or romantic involvement between the related entities.
-
C.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
D.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
E.
romanStatus
Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:02 p.m.