Triple
T31499163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berching |
E803627
|
entity |
| Predicate | hasTownWall |
P164891
|
FINISHED |
| Object | largely intact 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: largely intact medieval fortifications | Statement: [Berching, hasTownWall, largely intact medieval fortifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTownWall Context triple: [Berching, hasTownWall, largely intact 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.
hasCityWallFunction
Indicates that an entity serves the functional role of a city wall, such as providing defense, enclosure, or boundary protection for an urban area.
-
C.
hasCityWallRole
Indicates that an entity holds or is assigned a specific functional role related to the construction, maintenance, defense, or administration of a city wall.
-
D.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
E.
hadCityWalls
chosen
Indicates that a city or settlement possessed defensive walls surrounding it.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 30, 2026, 9:43 p.m.