Triple
T35381876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosra archaeological site |
E1022669
|
entity |
| Predicate | becameRomanColonyInCentury |
P118366
|
FINISHED |
| Object | 2nd century |
—
|
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: 2nd century | Statement: [Bosra archaeological site, becameRomanColonyInCentury, 2nd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameRomanColonyInCentury Context triple: [Bosra archaeological site, becameRomanColonyInCentury, 2nd century]
-
A.
becameRomanColony
chosen
Indicates that a place or community transitioned into the formal status of a Roman colony under Roman authority.
-
B.
approximateRomanConquestCentury
Indicates the approximate century in which the Romans conquered or gained control over a given entity.
-
C.
administeredColonyInCentury
Indicates that a governing entity administered control over a colony during a specified century.
-
D.
underRomanRuleBecame
Indicates that an entity, once under Roman political or administrative control, subsequently transformed into or was reconstituted as another specified entity.
-
E.
grantedColonyStatusInCentury
Indicates that an entity was officially granted the status of a colony during a specified century.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.