Triple

T26410931
Position Surface form Disambiguated ID Type / Status
Subject Lampedusa E663956 entity
Predicate hasPort P35 FINISHED
Object Port of Lampedusa
The Port of Lampedusa is a small Mediterranean harbor on the Italian island of Lampedusa that serves as a key fishing, ferry, and migrant landing point between Europe and North Africa.
E663956 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 Lampedusa | Statement: [Lampedusa, hasPort, Port of Lampedusa]
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 Lampedusa
Triple: [Lampedusa, hasPort, Port of Lampedusa]
Generated description
The Port of Lampedusa is a small Mediterranean harbor on the Italian island of Lampedusa that serves as a key fishing, ferry, and migrant landing point between Europe and North Africa.

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_69ee883931888190901be96d75ee23cc completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f6113143f481909c64dfc1975e3a59 completed May 2, 2026, 2:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11c7fe2c988190b0a00237f437105a completed May 23, 2026, 3:30 p.m.
NEDg Description generation batch_6a11c873b0d4819082b1c2e6859767ff completed May 23, 2026, 3:32 p.m.
NED2 Entity disambiguation (via description) batch_6a11c901b7c48190a86f5989c70ab615 completed May 23, 2026, 3:34 p.m.
Created at: April 26, 2026, 11:38 p.m.