Triple

T36399783
Position Surface form Disambiguated ID Type / Status
Subject Rupea E896589 entity
Predicate hasLandmark P105 FINISHED
Object Rupea Citadel
Rupea Citadel is a medieval hilltop fortress in Brașov County, Romania, known for its well-preserved defensive walls and panoramic views over the surrounding Transylvanian landscape.
E2185998 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: Rupea Citadel | Statement: [Rupea, hasLandmark, Rupea Citadel]
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: Rupea Citadel
Triple: [Rupea, hasLandmark, Rupea Citadel]
Generated description
Rupea Citadel is a medieval hilltop fortress in Brașov County, Romania, known for its well-preserved defensive walls and panoramic views over the surrounding Transylvanian landscape.

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_69f76e53b81081908d3b81860593f38a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bd14f67c8190a87d049aba53a0a3 completed May 3, 2026, 9:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39cfbf477c8190a3338e655514dfaa completed June 23, 2026, 12:13 a.m.
NEDg Description generation batch_6a39d3a0c36c8190bda5c37a3466cd2b completed June 23, 2026, 12:30 a.m.
NED2 Entity disambiguation (via description) batch_6a39d48a4d8081909f1154a9c923663b completed June 23, 2026, 12:34 a.m.
Created at: May 3, 2026, 4:10 p.m.