Triple

T37700912
Position Surface form Disambiguated ID Type / Status
Subject Detached Mole E939057 entity
Predicate hasPart P35 FINISHED
Object Detached Mole Lighthouse
Detached Mole Lighthouse is a navigational beacon situated on the Detached Mole breakwater in Gibraltar, guiding maritime traffic entering and leaving the harbor.
E2240760 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: Detached Mole Lighthouse | Statement: [Detached Mole, hasPart, Detached Mole Lighthouse]
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: Detached Mole Lighthouse
Triple: [Detached Mole, hasPart, Detached Mole Lighthouse]
Generated description
Detached Mole Lighthouse is a navigational beacon situated on the Detached Mole breakwater in Gibraltar, guiding maritime traffic entering and leaving the harbor.

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_69f76eda6ae48190b3111071eeacc038 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbae259fdc8190b22a1734e394d191 completed May 6, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40d672c314819087177c2861174830 completed June 28, 2026, 8:08 a.m.
NEDg Description generation batch_6a40d88e2bf48190ba6b3040ea8559b8 completed June 28, 2026, 8:17 a.m.
NED2 Entity disambiguation (via description) batch_6a40d8f9142081908a71318aad0e4c8b completed June 28, 2026, 8:19 a.m.
Created at: May 3, 2026, 4:18 p.m.