Triple
T32714919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetia et Histria |
E836494
|
entity |
| Predicate | romanAdministrativeNumber |
P7465
|
FINISHED |
| Object | Regio X |
—
|
NE NERFINISHED |
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: Regio X | Statement: [Venetia et Histria, romanAdministrativeNumber, Regio X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanAdministrativeNumber Context triple: [Venetia et Histria, romanAdministrativeNumber, Regio X]
-
A.
roleInRomanSystem
Indicates that one entity holds a specific function, position, or status within the structure or hierarchy of the Roman system.
-
B.
RomanNumeral
chosen
Indicates that something is represented or written using the Roman numeral system.
-
C.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
D.
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.
-
E.
sideRoman
Indicates that one entity is located on the Roman (Latin-script) side or version of another entity, typically in contrast to a non-Roman or alternative script side.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:11 a.m.