Triple
T27450895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Street |
E692435
|
entity |
| Predicate | hasAssociatedLanguagePair |
P169935
|
FINISHED |
| Object | English–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: English–Swedish | Statement: [King’s Street, hasAssociatedLanguagePair, English–Swedish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedLanguagePair Context triple: [King’s Street, hasAssociatedLanguagePair, English–Swedish]
-
A.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
-
B.
hasCommonTranslationLanguage
Indicates that two entities share at least one language into which both can be or have been translated.
-
C.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
-
D.
hasLanguageOfSide
Indicates that an entity uses or is associated with a particular language on a specific side or aspect (e.g., one side of a bilingual object or interface).
-
E.
coexistsWithLanguage
Indicates that one entity exists or functions alongside a particular language at the same time, without excluding or replacing it.
- F. None of above. chosen
Provenance (4 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 12:47 p.m.