Triple
T3056926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Utrecht |
E60503
|
entity |
| Predicate | containsAdministrativeTerritorialEntity |
P747
|
FINISHED |
| Object | Montfoort |
E525291
|
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: Montfoort | Statement: [Province of Utrecht, containsAdministrativeTerritorialEntity, Montfoort]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Montfoort Context triple: [Province of Utrecht, containsAdministrativeTerritorialEntity, Montfoort]
-
A.
Montfoort
chosen
Montfoort is a small historic town in the Dutch province of Utrecht, known for its medieval center and riverside setting.
-
B.
Rijkevoort
Rijkevoort is a village in the Dutch province of North Brabant, known for its rural character and location near the German border.
-
C.
Zutphen
Zutphen is a historic city in the eastern Netherlands known for its well-preserved medieval center and location along the river IJssel.
-
D.
Schoonhoven
Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
-
E.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e13f16c81909e11ed1444c71151 |
completed | March 8, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bff960da7c8190a72458b56f6c5c52 |
completed | March 22, 2026, 2:14 p.m. |
Created at: March 8, 2026, 3:02 p.m.