Triple
T17107350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Hellendoorn |
E415134
|
entity |
| Predicate | hasVillage |
P4011
|
FINISHED |
| Object | Marle |
E1248540
|
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: Marle | Statement: [municipality of Hellendoorn, hasVillage, Marle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marle Context triple: [municipality of Hellendoorn, hasVillage, Marle]
-
A.
Marle
Marle is a medieval French lordship or territory historically associated with the powerful noble Enguerrand III, Lord of Coucy.
-
B.
Marle
chosen
Marle is a small village in the Dutch municipality of Hellendoorn in the province of Overijssel.
-
C.
Mapragg
Mapragg is a small settlement in the municipality of Pfäfers in the canton of St. Gallen, Switzerland.
-
D.
Modara
Modara is a coastal urban neighborhood in Colombo, Sri Lanka, known for its port-adjacent location and dense residential and commercial activity.
-
E.
Thalgau
Thalgau is a municipality in the Austrian state of Salzburg, known for its scenic Alpine surroundings and proximity to the city of Salzburg.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc280b0c8190b9e620b90e0d4b40 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014143edb081909509c5435d392dd0 |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:35 a.m.