Triple
T17264351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engelbert II of Berg |
E419085
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Berg |
E287565
|
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: Berg | Statement: [Engelbert II of Berg, placeOfBirth, Berg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berg Context triple: [Engelbert II of Berg, placeOfBirth, Berg]
-
A.
Berg
Berg is a small Bavarian town on the shores of Lake Starnberg in southern Germany, known for its scenic lakeside setting and historical connections to King Ludwig II.
-
B.
Berg
chosen
Berg was a historical German territorial entity that gave its name to the later Grand Duchy of Berg in the Rhineland region.
-
C.
Berg
Berg is a surname most famously associated with Alban Berg, the influential Austrian composer of the Second Viennese School.
-
D.
Berg
Berg is a small town in eastern Luxembourg that serves as the administrative center of the commune of Betzdorf.
-
E.
Berge
Berge is a Norwegian surname most notably borne by politician Gunnar Berge.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4432fc81908fd90865822af1fa |
completed | April 19, 2026, 1:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0171054f388190bf068ca2e6b88458 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:40 a.m.