Triple
T38098717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zofingen |
E951316
|
entity |
| Predicate | hasHistoricCityWall |
P127567
|
FINISHED |
| Object | medieval fortifications |
—
|
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 fortifications | Statement: [Zofingen, hasHistoricCityWall, medieval fortifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCityWall Context triple: [Zofingen, hasHistoricCityWall, medieval fortifications]
-
A.
hasCityWallsFrom
Indicates that a city’s defensive walls originate from, or were constructed starting at, a specified source location or structure.
-
B.
hasCityWallsFromPeriod
chosen
Indicates that a city possesses defensive walls that date from a specified historical period.
-
C.
hadCityWalls
Indicates that a city or settlement possessed defensive walls surrounding it.
-
D.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
E.
hasHistoricTownWallsRemnants
Indicates that remnants of historic town walls are present and associated with the subject 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: May 3, 2026, 4:21 p.m.