Triple
T8781441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brescia |
E208736
|
entity |
| Predicate | wasRomanMunicipium |
P50574
|
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: [Brescia, wasRomanMunicipium, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRomanMunicipium Context triple: [Brescia, wasRomanMunicipium, true]
-
A.
wasRomanTown
chosen
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
-
B.
laterRomanAdministrativeUnit
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
-
C.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman period.
-
D.
wasRomanFort
Indicates that the subject functioned as a Roman military fort at some point in time.
-
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.
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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f55b7b08190ab3e18cd634a144b |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.