Triple

T29679129
Position Surface form Disambiguated ID Type / Status
Subject War with the Roman Empire in Nubia E750902 entity
Predicate location P40 FINISHED
Object Nile frontier
The Nile frontier was the southern boundary region of Roman-controlled Egypt along the Nile River, marking the empire’s contested border with Nubian kingdoms.
E1884655 NE 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: Nile frontier | Statement: [War with the Roman Empire in Nubia, location, Nile frontier]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Nile frontier
Triple: [War with the Roman Empire in Nubia, location, Nile frontier]
Generated description
The Nile frontier was the southern boundary region of Roman-controlled Egypt along the Nile River, marking the empire’s contested border with Nubian kingdoms.

Provenance (5 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_69f672608bf8819092efc616e42a361b completed May 2, 2026, 9:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a26c8dd15e88190af6b40ac2bc37c1c completed June 8, 2026, 1:51 p.m.
NEDg Description generation batch_6a26cd166f508190918662ab94184d6c completed June 8, 2026, 2:09 p.m.
NED2 Entity disambiguation (via description) batch_6a26daef2220819081ba427eb07b30e6 completed June 8, 2026, 3:08 p.m.
Created at: April 28, 2026, 7:09 p.m.