Triple
T12653349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domkerk |
E302219
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | Domkerk |
E302219
|
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: Domkerk | Statement: [Domkerk, nativeName, Domkerk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Domkerk Context triple: [Domkerk, nativeName, Domkerk]
-
A.
Domkerk
chosen
Domkerk is the historic Gothic cathedral in Utrecht that once served as the seat of the bishop and remains one of the city's most prominent landmarks.
-
B.
Ouderkerk
Ouderkerk was a former Dutch municipality in the province of South Holland that later became part of the municipality of Krimpenerwaard.
-
C.
Hoedekenskerke
Hoedekenskerke is a small village in the Dutch province of Zeeland, known for its rural character and location along the Western Scheldt.
-
D.
Leegkerk
Leegkerk is a small village in the province of Groningen in the Netherlands, known for its historic rural character and proximity to the city of Groningen.
-
E.
Grijpskerk
Grijpskerk is a village in the Dutch province of Groningen, known historically as a local agricultural and railway hub.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96160730c81909e1aa3efb51bf159 |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6688104d48190939933b93b7e60cc |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:18 p.m.