Triple
T19473223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAL Saal am Lindaplatz |
E487175
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object |
SAL
SAL is a cultural and event venue located at Saal am Lindaplatz, commonly referred to by its abbreviation.
|
E1378306
|
NE FINISHED |
How this triple was built (4 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: SAL | Statement: [SAL Saal am Lindaplatz, hasAbbreviation, SAL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SAL Context triple: [SAL Saal am Lindaplatz, hasAbbreviation, SAL]
-
A.
SAL
SAL is the three-letter IATA airport code for El Salvador International Airport, the main international gateway to El Salvador.
-
B.
SAL
SAL is the three-letter National Rail station code assigned to Salisbury railway station in Wiltshire, England.
-
C.
SAL
SAL is the standard abbreviation for Salavat Yulaev Ufa, a professional ice hockey team based in Ufa, Russia, that competes in the Kontinental Hockey League (KHL).
-
D.
SAL
SAL is the commonly used abbreviation for the Society of Antiquaries of London, a scholarly organization dedicated to the study and preservation of the material remains of the past.
-
E.
SAL (historic)
SAL (historic) is an old postal abbreviation formerly used in the United Kingdom to denote the historic county of Shropshire, traditionally known as Salop.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SAL Triple: [SAL Saal am Lindaplatz, hasAbbreviation, SAL]
Generated description
SAL is a cultural and event venue located at Saal am Lindaplatz, commonly referred to by its abbreviation.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SAL Target entity description: SAL is a cultural and event venue located at Saal am Lindaplatz, commonly referred to by its abbreviation.
-
A.
SAL
SAL is the three-letter IATA airport code for El Salvador International Airport, the main international gateway to El Salvador.
-
B.
SAL
SAL is the commonly used abbreviation for the Society of Antiquaries of London, a scholarly organization dedicated to the study and preservation of the material remains of the past.
-
C.
SAL
SAL is the three-letter National Rail station code assigned to Salisbury railway station in Wiltshire, England.
-
D.
SAL
SAL is the standard abbreviation for Salavat Yulaev Ufa, a professional ice hockey team based in Ufa, Russia, that competes in the Kontinental Hockey League (KHL).
-
E.
SAL (historic)
SAL (historic) is an old postal abbreviation formerly used in the United Kingdom to denote the historic county of Shropshire, traditionally known as Salop.
- F. None of above. chosen
Provenance (5 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633ea604c8190a2feacb709b7ca27 |
completed | April 20, 2026, 2:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07404fd4348190bc2efbebc7828716 |
completed | May 15, 2026, 3:48 p.m. |
| NEDg | Description generation | batch_6a074155addc8190a80e37d8f9d537a8 |
completed | May 15, 2026, 3:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0741e454a48190ac03aa458ca2b3b3 |
completed | May 15, 2026, 3:55 p.m. |
Created at: April 10, 2026, 1:39 p.m.