Triple

T26099983
Position Surface form Disambiguated ID Type / Status
Subject Moroccan national port system E658370 entity
Predicate hasPart P35 FINISHED
Object Port of Tan-Tan
The Port of Tan-Tan is a regional Moroccan seaport on the Atlantic coast that serves primarily as a hub for fishing, trade, and local economic activity.
E1737745 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: Port of Tan-Tan | Statement: [Moroccan national port system, hasPart, Port of Tan-Tan]
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: Port of Tan-Tan
Triple: [Moroccan national port system, hasPart, Port of Tan-Tan]
Generated description
The Port of Tan-Tan is a regional Moroccan seaport on the Atlantic coast that serves primarily as a hub for fishing, trade, and local economic activity.

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_69ee5bc09c288190bc42a11972841383 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f6073a39408190994ac1c8983a7c0b completed May 2, 2026, 2:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe4969fc8190b739c445cd553a4c completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11ffc02be08190bd5e8e5e6c7be000 completed May 23, 2026, 7:28 p.m.
NED2 Entity disambiguation (via description) batch_6a1200717d2881909d413b5dca4b8090 completed May 23, 2026, 7:30 p.m.
Created at: April 26, 2026, 7:54 p.m.