Triple
T8534259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissewaard |
E202035
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | NL |
E154307
|
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: NL | Statement: [Nissewaard, hasVehicleRegistrationCode, NL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NL Context triple: [Nissewaard, hasVehicleRegistrationCode, NL]
-
A.
NL
chosen
NL is the international vehicle registration code for the Netherlands, a country in Western Europe known for its flat landscape, canals, and historic cities.
-
B.
NL
NL is the commonly used abbreviation for Major League Baseball’s National League, one of its two primary professional baseball leagues in North America.
-
C.
NL
NL is the official two-letter Canada Post abbreviation for the province of Newfoundland and Labrador.
-
D.
NL
NL is the top-tier professional ice hockey league in Switzerland, featuring the country’s leading clubs and players.
-
E.
NL-NB
NL-NB is the ISO 3166-2 code representing the Dutch province of North Brabant.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a0ccd4819097b41d0dfb1c5018 |
completed | March 31, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6d7aa3a881909bfdd3536dbc4ec7 |
completed | April 2, 2026, 1:22 p.m. |
Created at: March 30, 2026, 6:17 p.m.