Triple
T4740306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Netherlands |
E105221
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Arnhem |
E12070
|
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: Arnhem | Statement: [Eastern Netherlands, hasMajorCity, Arnhem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arnhem Context triple: [Eastern Netherlands, hasMajorCity, Arnhem]
-
A.
Arnhem
chosen
Arnhem is a city in the eastern Netherlands best known as the site of a major World War II battle during Operation Market Garden.
-
B.
Leeuwarden
Leeuwarden is a historic city in the northern Netherlands, known as the capital of the province of Friesland and for its rich cultural and architectural heritage.
-
C.
Roermond
Roermond is a historic city in the southeastern Netherlands known for its medieval architecture, prominent churches, and large designer outlet shopping center.
-
D.
Papendrecht
Papendrecht is a Dutch town situated on the river Merwede in the province of South Holland, known for its residential character and proximity to the city of Dordrecht.
-
E.
Gorinchem
Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6486f8608190908e43b777810c44 |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be43ab20848190879de3a0d6366523 |
completed | March 21, 2026, 7:07 a.m. |
Created at: March 20, 2026, 1:19 p.m.