Triple
T2891716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LUSU |
E63840
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | LUSU |
E63840
|
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: LUSU | Statement: [LUSU, acronym, LUSU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LUSU Context triple: [LUSU, acronym, LUSU]
-
A.
LUSU
chosen
LUSU is the students' union representing and supporting students at Lancaster University in the United Kingdom.
-
B.
Ludes
Ludes is a wine-producing village in France’s Champagne region, known for its vineyards on the Montagne de Reims.
-
C.
Lusser
Lusser is a German surname most notably associated with engineer Robert Lusser, known for his contributions to aeronautics and reliability engineering.
-
D.
Lu
Lu is the traditional abbreviation and historical name used to refer to China’s Shandong province.
-
E.
Luss
Luss is a picturesque conservation village on the western shore of Loch Lomond in Scotland, known for its traditional stone cottages and role as a popular tourist destination within the Loch Lomond and The Trossachs National Park.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe060f49c8190bc804614a141c738 |
completed | March 7, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0317e15248190bade0f0fd930581a |
completed | March 10, 2026, 2:58 p.m. |
Created at: March 6, 2026, 10:07 p.m.