Triple
T37416164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Næstved Nord Station |
E929714
|
entity |
| Predicate | hasAbbreviationLanguageCode |
P183905
|
FINISHED |
| Object | da |
—
|
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: da | Statement: [Næstved Nord Station, hasAbbreviationLanguageCode, da]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationLanguageCode Context triple: [Næstved Nord Station, hasAbbreviationLanguageCode, da]
-
A.
isAbbreviationInLanguage
chosen
Indicates that a given abbreviation is used and recognized within a specified natural language.
-
B.
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).
-
C.
hasCountryAbbreviation
Indicates that an entity is associated with a specific standardized abbreviated form of a country’s name.
-
D.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
E.
hasAcronymExpansionLanguage
Indicates that a specified language is the language in which an acronym’s full expansion is expressed.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.