Triple

T24131818
Position Surface form Disambiguated ID Type / Status
Subject Cervia E597973 entity
Predicate hasLandmark P105 FINISHED
Object Port Canal of Cervia
The Port Canal of Cervia is a historic maritime waterway and harbor area in the Italian town of Cervia, known for its traditional fishing activity and picturesque waterfront.
E1621251 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 Canal of Cervia | Statement: [Cervia, hasLandmark, Port Canal of Cervia]
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 Canal of Cervia
Triple: [Cervia, hasLandmark, Port Canal of Cervia]
Generated description
The Port Canal of Cervia is a historic maritime waterway and harbor area in the Italian town of Cervia, known for its traditional fishing activity and picturesque waterfront.

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_69e288c808b881909fed7d18f04bcbbe completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1df78b6f08190809fc154110fa201 completed April 29, 2026, 10:37 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fad1f810881909a820e56ec13b58c completed May 22, 2026, 1:10 a.m.
NEDg Description generation batch_6a0fae6318c8819099bf0565a01b5312 completed May 22, 2026, 1:16 a.m.
NED2 Entity disambiguation (via description) batch_6a0faf073c088190bbf21e4dd0434fc1 completed May 22, 2026, 1:19 a.m.
Created at: April 17, 2026, 11:25 p.m.