Triple
T5216659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glevum |
E117767
|
entity |
| Predicate | coloniaStatusGrantedBy |
P42435
|
FINISHED |
| Object | Roman authorities |
—
|
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: Roman authorities | Statement: [Glevum, coloniaStatusGrantedBy, Roman authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coloniaStatusGrantedBy Context triple: [Glevum, coloniaStatusGrantedBy, Roman authorities]
-
A.
foundedAsColonyFor
Indicates that one entity was established as a colony specifically for the benefit, use, or purposes of another entity.
-
B.
isColonialFoundationOf
Indicates that one entity was established as a colony that later developed into or served as the origin of the other entity.
-
C.
formerColonyEstablishedIn
Indicates that a former colony was originally established in a specified year or time period.
-
D.
formerColonialStatus
Indicates that one entity previously held colonial authority or control over another entity, but that colonial relationship has since ended.
-
E.
colonialDesignation
chosen
Indicates that one entity assigns or holds a status, name, or classification for another entity within a colonial or colonially imposed framework.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a93fcc08190a1d2d025b4365d5a |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.