Triple
T15116556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SALA |
E361054
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | SALA |
E361054
|
NE 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: SALA | Statement: [SALA, acronym, SALA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SALA Context triple: [SALA, acronym, SALA]
-
A.
SALA
chosen
SALA is an arts festival, known as the South Australian Living Artists Festival, that showcases visual art across venues throughout South Australia.
-
B.
Sala
Sala is a small historic town in central Sweden known for its former silver mine and well-preserved wooden architecture.
-
C.
SAL
SAL is the three-letter IATA airport code for El Salvador International Airport, the main international gateway to El Salvador.
-
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
SAL is the three-letter National Rail station code assigned to Salisbury railway station in Wiltshire, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7eee6e8819092657c4006456135 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:05 a.m.