Triple
T4912421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm bus network |
E110263
|
entity |
| Predicate | primaryLanguageOnSignage |
P4196
|
FINISHED |
| Object | Swedish |
—
|
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: Swedish | Statement: [Stockholm bus network, primaryLanguageOnSignage, Swedish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLanguageOnSignage Context triple: [Stockholm bus network, primaryLanguageOnSignage, Swedish]
-
A.
officialLanguageOfSignage
Indicates that a particular language is the one officially used on public signs and signage within a given place or context.
-
B.
tertiaryLanguageOfSignage
Indicates that a language is used as the third-most prominent language on signage in a given context or location.
-
C.
languageOfSignage
chosen
Indicates the language used on signs or written displays associated with an entity.
-
D.
primaryLanguageSide1
Indicates that the specified language is the main or dominant language associated with the first participant or side in a relationship.
-
E.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.