Triple
T5944735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knudstrup |
E132251
|
entity |
| Predicate | birthplaceOf |
P1
|
FINISHED |
| Object | Tycho Brahe |
E22915
|
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: Tycho Brahe | Statement: [Knudstrup, birthplaceOf, Tycho Brahe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tycho Brahe Context triple: [Knudstrup, birthplaceOf, Tycho Brahe]
-
A.
Tycho Brahe
chosen
Tycho Brahe was a Danish nobleman and astronomer whose precise naked-eye observations of the heavens greatly improved astronomical data and paved the way for Kepler’s laws of planetary motion.
-
B.
Abraham Brahe
Abraham Brahe was a Swedish nobleman of the influential Brahe family and the father of statesman and governor-general Per Brahe the Younger.
-
C.
Jørgen Brahe
Jørgen Brahe was a Danish nobleman and foster father of the astronomer Tycho Brahe, playing a key role in raising and educating him.
-
D.
Brahe
Brahe is a noble Scandinavian surname most famously associated with the Danish astronomer Tycho Brahe and his influential family.
-
E.
Otte Brahe
Otte Brahe was a 16th-century Danish nobleman and landowner best known as the father of the astronomer Tycho Brahe.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03937b4a88190819a1fd63fc3d3ed |
completed | March 22, 2026, 6:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11cc81b3081908a35c4230eba3f06 |
completed | March 23, 2026, 10:58 a.m. |
Created at: March 22, 2026, 4:01 p.m.