Triple
T22139973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DK (droga krajowa) |
E547130
|
entity |
| Predicate | hasAbbreviationOnMaps |
P63320
|
FINISHED |
| Object | DK followed by route number |
—
|
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: DK followed by route number | Statement: [DK (droga krajowa), hasAbbreviationOnMaps, DK followed by route number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationOnMaps Context triple: [DK (droga krajowa), hasAbbreviationOnMaps, DK followed by route number]
-
A.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
B.
usesAbbreviationIn
chosen
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
C.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
D.
hasAbbreviationForRegion
Indicates that one entity is used as the standard abbreviated form of the name of a particular region.
-
E.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bda1208190b851ae5c68b760e9 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.