Triple
T35960254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veromandui |
E1039974
|
entity |
| Predicate | romanCivitasCapital |
P184477
|
FINISHED |
| Object | Augusta Veromanduorum |
—
|
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: Augusta Veromanduorum | Statement: [Veromandui, romanCivitasCapital, Augusta Veromanduorum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanCivitasCapital Context triple: [Veromandui, romanCivitasCapital, Augusta Veromanduorum]
-
A.
romanCivitasName
Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
-
B.
romanProvinceCapital
Indicates that one place served as the administrative capital of a specified Roman province.
-
C.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
D.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
E.
preRomanCenterOf
Indicates that a place served as the primary political, cultural, or administrative center of a region or community before the establishment of Roman control or influence.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:07 p.m.