Triple

T33099813
Position Surface form Disambiguated ID Type / Status
Subject Moroccan railway network E847009 entity
Predicate hasMainLine P3492 FINISHED
Object Fes–Oujda line
The Fes–Oujda line is a major Moroccan railway route linking the inland city of Fes with the eastern city of Oujda near the Algerian border, serving as a key corridor for passenger and freight transport.
E2039967 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: Fes–Oujda line | Statement: [Moroccan railway network, hasMainLine, Fes–Oujda line]
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: Fes–Oujda line
Triple: [Moroccan railway network, hasMainLine, Fes–Oujda line]
Generated description
The Fes–Oujda line is a major Moroccan railway route linking the inland city of Fes with the eastern city of Oujda near the Algerian border, serving as a key corridor for passenger and freight transport.

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_69f3495686508190b76bf20fa5e00bf7 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6ac00488190876b0db0fb5fb29b completed May 3, 2026, 5:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3525b085b4819084f402104a641e65 completed June 19, 2026, 11:19 a.m.
NEDg Description generation batch_6a3527f6bb4c8190adb0e462f5d9f802 completed June 19, 2026, 11:28 a.m.
NED2 Entity disambiguation (via description) batch_6a3528d396dc8190941db4ef11a450d3 completed June 19, 2026, 11:32 a.m.
Created at: May 1, 2026, 1:26 a.m.