Triple

T25898305
Position Surface form Disambiguated ID Type / Status
Subject Deir el Qamar E652530 entity
Predicate hasLandmark P105 FINISHED
Object Fakhreddine Mosque
Fakhreddine Mosque is a historic Ottoman-era mosque in the Lebanese village of Deir el Qamar, notable for its distinctive architecture and cultural significance.
E1707316 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: Fakhreddine Mosque | Statement: [Deir el Qamar, hasLandmark, Fakhreddine Mosque]
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: Fakhreddine Mosque
Triple: [Deir el Qamar, hasLandmark, Fakhreddine Mosque]
Generated description
Fakhreddine Mosque is a historic Ottoman-era mosque in the Lebanese village of Deir el Qamar, notable for its distinctive architecture and cultural significance.

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_69e7ab3c6cc081908de59bfcc28ec19d completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6038777008190ae54d57d622824f9 completed May 2, 2026, 2 p.m.
NED1 Entity disambiguation (via context triple) batch_6a111afbccf0819081bf92bf73f1a006 completed May 23, 2026, 3:11 a.m.
NEDg Description generation batch_6a111bd7e1188190b3275dc1efe4bfb3 completed May 23, 2026, 3:15 a.m.
NED2 Entity disambiguation (via description) batch_6a111cbb1ed88190a4980f8fc8a0a19f completed May 23, 2026, 3:19 a.m.
Created at: April 22, 2026, 8:23 a.m.