Triple
T22316956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bockenheimer Warte |
E551669
|
entity |
| Predicate | isPhotographicLandmark |
P23855
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bockenheimer Warte, isPhotographicLandmark, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhotographicLandmark Context triple: [Bockenheimer Warte, isPhotographicLandmark, true]
-
A.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
-
B.
hasPhotographicSignificance
chosen
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
C.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
D.
isSocialLandmark
Indicates that a place functions as a notable social gathering point or reference location within a community or area.
-
E.
oftenPhotographedAt
Indicates that an entity is frequently the subject of photographs taken at a particular location or during a specific event.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157535eb48190adbefbb619cb5fcd |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.