Triple
T8896426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blixem |
E211815
|
entity |
| Predicate | listedWith |
P31874
|
FINISHED |
| Object | Donder |
E195056
|
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: Donder | Statement: [Blixem, listedWith, Donder]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Donder Context triple: [Blixem, listedWith, Donder]
-
A.
Donder
chosen
Donder is one of Santa Claus’s traditional reindeer, often listed alongside Dancer and the other members of his Christmas sleigh team.
-
B.
Estwedus
Estwedus is the ancient name of the city now known as Aspendos, a prominent Greco-Roman settlement in Pamphylia, famed for its well-preserved Roman theater in modern-day Turkey.
-
C.
Ösel
Ösel is the historical German and Swedish name for Saaremaa, the largest island of Estonia in the Baltic Sea.
-
D.
Poulus
Poulus is a personal name variant derived from the given name Poul.
-
E.
Everardus
Everardus is a Latinized given name historically used in medieval and early modern Europe, derived from the Germanic name Everard.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61bfec0881908e4ef5b7f0e6b542 |
completed | April 1, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfac02974881908a7e8d9cfa47e624 |
completed | April 3, 2026, 12:01 p.m. |
Created at: March 30, 2026, 6:54 p.m.