Triple
T35630989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clock Tower (Sighișoara) |
E1029583
|
entity |
| Predicate | locatedInCitadel |
P28661
|
FINISHED |
| Object | medieval citadel of Sighișoara |
—
|
LITERAL 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: medieval citadel of Sighișoara | Statement: [Clock Tower (Sighișoara), locatedInCitadel, medieval citadel of Sighișoara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCitadel Context triple: [Clock Tower (Sighișoara), locatedInCitadel, medieval citadel of Sighișoara]
-
A.
locatedInFortress
chosen
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
B.
roleInCitadel
Indicates the specific function, position, or responsibility an entity holds within a citadel or fortified complex.
-
C.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
D.
citadelAlsoCalled
Indicates that a citadel is known or referred to by an alternative name or alias.
-
E.
fortressLocatedOn
Indicates that a fortress is situated on or atop a specified geographic feature, structure, or location.
- F. None of above.
Provenance (3 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.