Triple
T29129536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germania Superior |
E738331
|
entity |
| Predicate | ceasedToExistAsProvince |
P25984
|
FINISHED |
| Object | early 5th 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: early 5th century CE | Statement: [Germania Superior, ceasedToExistAsProvince, early 5th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedToExistAsProvince Context triple: [Germania Superior, ceasedToExistAsProvince, early 5th century CE]
-
A.
formerProvince
chosen
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
-
B.
establishedAsProvinceIn
Indicates that an entity was formally designated or created as a province in a specified year or time period.
-
C.
laterProvinceName
Indicates that an entity (such as a region or administrative unit) is known by a different province name at a later point in time.
-
D.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
E.
abolishedAsState
Indicates that a political entity or territorial unit ceased to exist in its former status as a state due to formal abolition.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:30 a.m.