Triple
T11282377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nijmegen Quarter |
E267094
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Zutphen Quarter |
E323979
|
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: Zutphen Quarter | Statement: [Nijmegen Quarter, borders, Zutphen Quarter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zutphen Quarter Context triple: [Nijmegen Quarter, borders, Zutphen Quarter]
-
A.
Zutphen
chosen
Zutphen is a historic city in the eastern Netherlands known for its well-preserved medieval center and location along the river IJssel.
-
B.
Begijnhof
Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
-
C.
Rijkevoort
Rijkevoort is a village in the Dutch province of North Brabant, known for its rural character and location near the German border.
-
D.
Nijmegen Quarter
Nijmegen Quarter was a historical administrative region centered around the city of Nijmegen within the medieval Duchy of Guelders in the Low Countries.
-
E.
Ridderkerk
Ridderkerk is a town and municipality in the western Netherlands, situated near Rotterdam in the province of South Holland.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e96e15708190b3a1cccfbbe65882 |
completed | April 9, 2026, 6:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f471490081909036362c58e1e727 |
completed | April 19, 2026, 3:27 p.m. |
Created at: April 8, 2026, 9:31 p.m.