Triple
T14265919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wedding, Berlin |
E353643
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Berlin |
E5567
|
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: Berlin | Statement: [Wedding, Berlin, partOf, Berlin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berlin Context triple: [Wedding, Berlin, partOf, Berlin]
-
A.
Berlin
Berlin is a small town in South Africa’s Eastern Cape province, situated within the Buffalo City Metropolitan Municipality near East London.
-
B.
Berlin
chosen
Berlin is the capital and largest city of Germany, historically significant as a focal point of Cold War tensions and a major cultural, political, and economic center in Europe.
-
C.
Berlin
Berlin is a charismatic, calculating, and morally ambiguous mastermind and heist leader in the Spanish television series "Money Heist" (La Casa de Papel).
-
D.
Berlin
Berlin is a major Ethereum network upgrade that introduced various gas cost optimizations and transaction processing improvements to enhance the blockchain’s efficiency and performance.
-
E.
Berlin
Berlin is a borough in Camden County, New Jersey, known as a suburban community within the Philadelphia metropolitan area.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6357a8188190ba518a486521052b |
completed | April 14, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd32497780819092e2d2ffe2a9dcaf |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:09 a.m.