Triple
T23022106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleki |
E573195
|
entity |
| Predicate | familyNameVariant |
P16885
|
FINISHED |
| Object | Teleky |
—
|
NE NERFINISHED |
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: Teleky | Statement: [Teleki, familyNameVariant, Teleky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teleky Context triple: [Teleki, familyNameVariant, Teleky]
-
A.
Teke
Teke is a Bantu language spoken primarily in the Republic of the Congo and neighboring Central African regions by the Teke people.
-
B.
Teke
Teke are a prominent Turkmen tribal group historically known for their influence in Central Asia and their famed Akhal-Teke horses.
-
C.
Teleki
chosen
Teleki is a Hungarian noble family name most notably associated with Pál Teleki, a geographer and two-time prime minister of Hungary in the early 20th century.
-
D.
Teves
Teves is an alternative Ashkenazi transliteration of the Hebrew month name Tevet, used in the Jewish calendar.
-
E.
Tecka
Tecka is a small town in the Chubut Province of Argentine Patagonia, serving as a local hub along regional road networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183ea23088190b2f42d9bf01514ac |
completed | April 29, 2026, 4:07 a.m. |
Created at: April 17, 2026, 3:52 p.m.