Triple
T4797938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P |
E106757
|
entity |
| Predicate | countryCodeSystem |
P45385
|
FINISHED |
| Object | Czech regional license plate codes |
—
|
LITERAL 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: Czech regional license plate codes | Statement: [P, countryCodeSystem, Czech regional license plate codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeSystem Context triple: [P, countryCodeSystem, Czech regional license plate codes]
-
A.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
-
B.
regionCodeSystem
chosen
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
C.
countryCodeManaged
Indicates that an entity is responsible for administering or controlling the specified country code.
-
D.
countryCodePart
Indicates that one entity is a segment or component of a standardized country code associated with another entity.
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
- F. None of above.
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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.