Triple
T29679153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War with the Roman Empire in Nubia |
E750902
|
entity |
| Predicate | frontierEstablishedAt |
P119702
|
FINISHED |
| Object | region around Qasr Ibrim |
—
|
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: region around Qasr Ibrim | Statement: [War with the Roman Empire in Nubia, frontierEstablishedAt, region around Qasr Ibrim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontierEstablishedAt Context triple: [War with the Roman Empire in Nubia, frontierEstablishedAt, region around Qasr Ibrim]
-
A.
establishesFrontier
chosen
Indicates the action or relationship by which a boundary or frontier is formally created, defined, or set between entities.
-
B.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
C.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
D.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
E.
fortEstablishedAt
Indicates that a fort was founded or set up at a specific location or time.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 7:09 p.m.