Triple
T29114604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luguvalium |
E737007
|
entity |
| Predicate | regionInRomanAdministration |
P95485
|
FINISHED |
| Object | Britannia |
—
|
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: Britannia | Statement: [Luguvalium, regionInRomanAdministration, Britannia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionInRomanAdministration Context triple: [Luguvalium, regionInRomanAdministration, Britannia]
-
A.
laterRomanAdministrativeUnit
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
-
B.
preRomanRegion
Indicates that a region existed or was defined in the period before Roman rule or influence.
-
C.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
D.
romanProvinceType
Indicates that an entity is classified as a specific type or category of Roman province.
-
E.
wasRomanProvince
chosen
Indicates that one entity functioned as a province under the authority or administration of the Roman Empire.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 28, 2026, 11:21 a.m.