Triple
T13715172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady of Leerdam |
E328877
|
entity |
| Predicate | linkedPlace |
P3158
|
FINISHED |
| Object | Leerdam |
—
|
NE NERFINISHED |
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: Leerdam | Statement: [Lady of Leerdam, linkedPlace, Leerdam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leerdam Context triple: [Lady of Leerdam, linkedPlace, Leerdam]
-
A.
Leerdam
chosen
Leerdam is a Dutch city renowned for its glassmaking tradition, located in the province of South Holland.
-
B.
Roosendaal
Roosendaal is a city in the southern Netherlands known as a regional center for commerce and transport near the Belgian border.
-
C.
Barendrecht
Barendrecht is a suburban town in the western Netherlands, located just south of Rotterdam and known for its residential character and logistics industry.
-
D.
Gorinchem
Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
-
E.
Apeldoorn
Apeldoorn is a city in the province of Gelderland in the Netherlands, known for the royal palace Het Loo and its historical ties to the Dutch monarchy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
Created at: April 9, 2026, 9:54 p.m.