Triple
T15983829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raad voor het Koninkrijk |
E387641
|
entity |
| Predicate | appliesToJurisdiction |
P82
|
FINISHED |
| Object | Nederland |
E864
|
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: Nederland | Statement: [Raad voor het Koninkrijk, appliesToJurisdiction, Nederland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nederland Context triple: [Raad voor het Koninkrijk, appliesToJurisdiction, Nederland]
-
A.
Nederland
Nederland is a small mountain town in Colorado known for its scenic setting near the Rocky Mountains and its quirky local culture.
-
B.
Netherlands
chosen
The Netherlands is a Western European country known for its low-lying geography, extensive canal systems, and historically significant role in global trade and European politics.
-
C.
Holland
Holland is a common English surname of Dutch origin, historically referring to people from the Holland region of the Netherlands.
-
D.
Holland
Holland is a historic coastal region in the western Netherlands that became the political and economic heartland of the emerging Dutch state.
-
E.
Holland
Holland is a regional less-than-truckload (LTL) freight carrier in the United States known for its operations in the Midwest and surrounding areas.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e15756d6488190ac35da00e96ce21d |
completed | April 16, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000ec329488190ab4269b6d94a983d |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 4:54 a.m.