Triple
T30486170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marienberg |
E775727
|
entity |
| Predicate | hasFortificationRemnant |
P22477
|
FINISHED |
| Object | town walls remains |
—
|
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: town walls remains | Statement: [Marienberg, hasFortificationRemnant, town walls remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFortificationRemnant Context triple: [Marienberg, hasFortificationRemnant, town walls remains]
-
A.
hasFortifications
chosen
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
B.
hasFortificationTarget
Indicates that a fortification action is directed toward or applied to a specific target entity.
-
C.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
D.
hasFortificationNearby
Indicates that one entity is located in proximity to, or within the immediate area of, a fortification structure associated with it.
-
E.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 8:13 p.m.