Triple
T6287933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius |
E140945
|
entity |
| Predicate | praenomenOfEthnicity |
P70697
|
FINISHED |
| Object | Roman |
—
|
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: Roman | Statement: [Publius, praenomenOfEthnicity, Roman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: praenomenOfEthnicity Context triple: [Publius, praenomenOfEthnicity, Roman]
-
A.
praenomenTransliteration
Indicates the transliterated form of a person's Latin praenomen (given name) from its original script into a standardized Latin-letter representation.
-
B.
praenomenLinkedDeity
Indicates that a person's praenomen (given name) is etymologically or culturally linked to, derived from, or associated with a particular deity.
-
C.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
-
D.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
E.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064182f60819093a8313e1dbf2763 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c06284848c8190a0151ff3e8682889 |
completed | March 22, 2026, 9:43 p.m. |
Created at: March 22, 2026, 4:26 p.m.