Triple
T2930865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronsdorf |
E78956
|
entity |
| Predicate | historicalMunicipalStatus |
P28623
|
FINISHED |
| Object | independent town |
—
|
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: independent town | Statement: [Ronsdorf, historicalMunicipalStatus, independent town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMunicipalStatus Context triple: [Ronsdorf, historicalMunicipalStatus, independent town]
-
A.
historicalStatusOf
chosen
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
B.
hasMunicipalStatusChange
Indicates that an entity undergoes a change in its official municipal status (e.g., creation, upgrade, downgrade, merger, or dissolution as a municipality).
-
C.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
D.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
E.
hasLocalGovernmentHistory
Indicates that an entity has a documented history or record of its local governmental structure, activities, or developments.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad980191388190ac2455a7d9867be3 |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.