Triple
T13770049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Lollius (consul 21 BCE) |
E330855
|
entity |
| Predicate | hasRomanTriaNomina |
P87811
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Marcus Lollius (consul 21 BCE), hasRomanTriaNomina, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanTriaNomina Context triple: [Marcus Lollius (consul 21 BCE), hasRomanTriaNomina, true]
-
A.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
B.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
C.
hasRomanNameStructure
chosen
Indicates that an entity’s name follows the conventional structural pattern of Roman naming (e.g., praenomen–nomen–cognomen or similar historically Roman forms).
-
D.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
E.
partOfRomanNamingSystem
Indicates that something functions as a component or element within the traditional Roman naming system.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0233ecc48190b934f085d2501eb1 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.