Triple
T28661926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vindonissa |
E725489
|
entity |
| Predicate | postRomanUse |
P133875
|
FINISHED |
| Object | continued civilian occupation in late antiquity |
—
|
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: continued civilian occupation in late antiquity | Statement: [Vindonissa, postRomanUse, continued civilian occupation in late antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRomanUse Context triple: [Vindonissa, postRomanUse, continued civilian occupation in late antiquity]
-
A.
postRomanReuse
chosen
Indicates that something originally from the Roman period is used, repurposed, or incorporated again in a later, post-Roman context.
-
B.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
C.
postRomanSuccessor
Indicates that one entity serves as the political or cultural successor to another entity following the end of Roman rule.
-
D.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
E.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:58 a.m.