Triple
T2317444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goslar |
E51097
|
entity |
| Predicate | wasFreeImperialCity |
P17968
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Goslar, wasFreeImperialCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFreeImperialCity Context triple: [Goslar, wasFreeImperialCity, true]
-
A.
wasFreeImperialCityOf
chosen
Indicates that an entity formerly held the status of a Free Imperial City within the Holy Roman Empire in relation to another specified entity (typically the empire or its imperial structure).
-
B.
liberatedCity
Indicates that an agent has freed a city from control, occupation, or oppression.
-
C.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
D.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
E.
wasImportantCityOf
Indicates that a city held significant importance or prominence within a specified larger political or geographic entity during a given time period.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.