Triple
T30268687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rügenwalde |
E769724
|
entity |
| Predicate | hasUrbanHistory |
P153247
|
FINISHED |
| Object | medieval town rights |
—
|
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 town rights | Statement: [Rügenwalde, hasUrbanHistory, medieval town rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanHistory Context triple: [Rügenwalde, hasUrbanHistory, medieval town rights]
-
A.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
B.
urbanHistoryFeature
Indicates a feature that plays a significant role in the historical development, events, or evolution of an urban area.
-
C.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
-
D.
isHistoricalCity
chosen
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
E.
hasUrbanInfluence
Indicates that one entity exerts or reflects the characteristics, impact, or style of an urban area on another entity.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d27d288190b66d52f002726551 |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:43 p.m.