Triple
T16749643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSJUMB |
E407039
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | LSJUMB |
E407039
|
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: LSJUMB | Statement: [LSJUMB, acronym, LSJUMB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LSJUMB Context triple: [LSJUMB, acronym, LSJUMB]
-
A.
LSJUMB
chosen
LSJUMB is the famously irreverent and high-energy marching band of Stanford University, known for its unconventional performances and humorous, often controversial style.
-
B.
LJS
LJS is the commonly used abbreviation for the Liberal Jewish Synagogue, a prominent progressive Jewish congregation in London.
-
C.
LJU
LJU is the UN/LOCODE designation for Ljubljana Jože Pučnik Airport, the main international airport serving Ljubljana, Slovenia.
-
D.
LPSJ
LPSJ is the ICAO airport code for São Jorge Airport, which serves the island of São Jorge in Portugal’s Azores archipelago.
-
E.
LJ
LJ is the third-generation model of the Holden Torana, a compact Australian car produced in the early 1970s and known for its performance-oriented variants.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa265a908190a87fa4612bfe6396 |
completed | April 18, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a522255c8190ab16d7ad233fcd3b |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 10, 2026, 5:21 a.m.