Triple
T4369836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegnitz |
E98867
|
entity |
| Predicate | hasRevetment |
P55810
|
FINISHED |
| Object | urban riverbank fortifications in Nuremberg |
—
|
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: urban riverbank fortifications in Nuremberg | Statement: [Pegnitz, hasRevetment, urban riverbank fortifications in Nuremberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevetment Context triple: [Pegnitz, hasRevetment, urban riverbank fortifications in Nuremberg]
-
A.
hasRenovation
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
-
B.
roofStatus
Indicates the current condition or state of a roof, such as whether it is intact, damaged, under repair, or replaced.
-
C.
hasReconstructionWork
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
D.
haveReconstructionWork
Indicates that an entity is undergoing or is associated with reconstruction or restoration work.
-
E.
hasAttic
Indicates that one entity (typically a building or house) includes or is equipped with an attic space.
- F. None of above. chosen
Provenance (4 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352052b388190b02cca9a3b480be4 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.