Triple
T12116592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leek |
E288577
|
entity |
| Predicate | hasDutchName |
P744
|
FINISHED |
| Object | Leek |
E288577
|
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: Leek | Statement: [Leek, hasDutchName, Leek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leek Context triple: [Leek, hasDutchName, Leek]
-
A.
Leek
Leek is a historic market town in Staffordshire, England, known for its textile heritage and picturesque location near the Peak District.
-
B.
Leek
chosen
Leek is a former municipality in the Dutch province of Groningen, known for its rural character and historic estates, that was incorporated into the municipality of Westerkwartier.
-
C.
Onions
Onions is an English surname most notably associated with Charles Talbut Onions, a prominent lexicographer and editor of the Oxford English Dictionary.
-
D.
Kale
Kale is a town in Myanmar’s Sagaing Region, known as a local commercial and transport hub in the country’s northwest.
-
E.
Kale
Kale is a district-level administrative area within Turkey, known for its location in Malatya Province in the Eastern Anatolia region.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9156921dc8190aa132b0ab3a7c184 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a75f77881908345a585a689f69f |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:49 p.m.