Triple
T35574490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lopodunum |
E1028035
|
entity |
| Predicate | timeOfRomanControl |
P88235
|
FINISHED |
| Object | 1st–3rd century CE |
—
|
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: 1st–3rd century CE | Statement: [Lopodunum, timeOfRomanControl, 1st–3rd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfRomanControl Context triple: [Lopodunum, timeOfRomanControl, 1st–3rd century CE]
-
A.
timeOfRomanPromotion
Indicates the specific time at which a Roman individual or entity received a promotion in status, rank, or office.
-
B.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
C.
approximateRomanConquestCentury
Indicates the approximate century in which the Romans conquered or gained control over a given entity.
-
D.
eraOfRomanConquest
chosen
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
E.
regionDuringEmpire
Indicates that a region existed within or was governed by a particular empire during a specified historical period.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:04 p.m.