Triple
T13704244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eemnes |
E328597
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Hilversum |
E475829
|
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: Hilversum | Statement: [Eemnes, hasNearbyCity, Hilversum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hilversum Context triple: [Eemnes, hasNearbyCity, Hilversum]
-
A.
Hilversum
chosen
Hilversum is a Dutch city known as the country’s main media and broadcasting center, located in the province of North Holland.
-
B.
Tilburg
Tilburg is a city in the southern Netherlands known historically as an industrial and textile center and now as a regional cultural and educational hub.
-
C.
Utrecht
Utrecht is a historic city and province in the central Netherlands, known for its medieval old town, canals, and role as a religious and cultural center.
-
D.
Utrecht
Utrecht is a small town in South Africa’s KwaZulu-Natal province, known for its scenic surroundings and historical significance dating back to the 19th century.
-
E.
Zoetermeer
Zoetermeer is a modern, rapidly grown satellite city of The Hague in the western Netherlands, known for its residential neighborhoods and light-rail connections.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad162158819089280ee1e6b5c2cf |
completed | April 13, 2026, 8:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00aade82788190a5f3cedbc22065c4 |
completed | May 10, 2026, 3:57 p.m. |
Created at: April 9, 2026, 9:54 p.m.