Triple
T17399840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berg Castle |
E423056
|
entity |
| Predicate | significantEventPlace |
P127335
|
FINISHED |
| Object | shore of Lake Starnberg near Berg Castle |
—
|
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: shore of Lake Starnberg near Berg Castle | Statement: [Berg Castle, significantEventPlace, shore of Lake Starnberg near Berg Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventPlace Context triple: [Berg Castle, significantEventPlace, shore of Lake Starnberg near Berg Castle]
-
A.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
significantVenueFor
Indicates that a venue plays an important or notable role in relation to a particular entity, event, or activity.
-
C.
significantPlaceType
Indicates the type or category of place that holds particular significance in relation to the subject.
-
D.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
E.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ac0596481908c400916d5c1b971 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.