Triple
T6936451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniBE |
E160564
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | UniBE |
E160564
|
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: UniBE | Statement: [UniBE, abbreviation, UniBE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UniBE Context triple: [UniBE, abbreviation, UniBE]
-
A.
UniBE
chosen
UniBE is the commonly used abbreviation for the University of Bern, a major public research university located in Bern, Switzerland.
-
B.
UniGe
UniGe is the commonly used abbreviation for the University of Genoa, a major public research university located in Genoa, Italy.
-
C.
UniFE
UniFE is the commonly used abbreviation for the University of Ferrara, a public research university located in Ferrara, Italy.
-
D.
UniPG
UniPG is the commonly used abbreviation for the University of Perugia, a historic Italian public university located in Perugia, Umbria.
-
E.
UniFR
UniFR is the commonly used abbreviation for the University of Fribourg, a bilingual (French and German) public university in Fribourg, Switzerland.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da5eacd8819083252aa1a42d2a5d |
completed | March 27, 2026, 7:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c75151d5e48190b2389ae9049d1454 |
completed | March 28, 2026, 3:56 a.m. |
Created at: March 27, 2026, 2:27 p.m.