Triple
T38195198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiser Wilhelm Tower |
E1005589
|
entity |
| Predicate | locatedOnSummitOf |
P142348
|
FINISHED |
| Object | Hohe Acht |
E306332
|
NE 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: Hohe Acht | Statement: [Kaiser Wilhelm Tower, locatedOnSummitOf, Hohe Acht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSummitOf Context triple: [Kaiser Wilhelm Tower, locatedOnSummitOf, Hohe Acht]
-
A.
locatedOnPeak
Indicates that one entity is situated at or on the summit or highest point of another entity (a peak).
-
B.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
C.
onSummitAreaOf
Indicates that one entity is located on the summit area (topmost surface or plateau) of another entity.
-
D.
isNamedSummitOf
Indicates that one entity is the officially designated summit (highest or principal point) of another entity, such as a mountain or geographic feature.
-
E.
hasStructureOnOrNearSummit
chosen
Indicates that a structure is present on the summit of something or in its immediate vicinity.
- F. None of above.
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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41853fab548190be4cc87a7a4809c3 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.