Triple
T7280442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Ultras |
E163132
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | Triglav |
E399790
|
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: Triglav | Statement: [European Ultras, includes, Triglav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Triglav Context triple: [European Ultras, includes, Triglav]
-
A.
Mount Triglav
chosen
Mount Triglav is Slovenia’s highest and most iconic mountain, a national symbol featured on the country’s coat of arms and flag.
-
B.
Turska gora
Turska gora is a prominent mountain peak in northern Slovenia known for its rugged alpine terrain and popular hiking and climbing routes.
-
C.
Jahorina
Jahorina is a prominent mountain in Bosnia and Herzegovina, best known as a major ski resort area and former venue for the 1984 Winter Olympics.
-
D.
Grossglockner
Grossglockner is the tallest mountain in Austria and a prominent peak of the Hohe Tauern range in the Central Eastern Alps.
-
E.
Sněžka
Sněžka is the highest mountain in the Czech Republic, located on the border with Poland in the Krkonoše range.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb339b1081909f648864e210f98e |
completed | March 27, 2026, 8:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e532a7f08190a5c0b1167dc0be44 |
completed | March 28, 2026, 2:26 p.m. |
Created at: March 27, 2026, 2:59 p.m.