Triple
T32910798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bükk National Park |
E841870
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Istállós-kő Cave
Istállós-kő Cave is a notable prehistoric cave and archaeological site in Hungary’s Bükk Mountains, renowned for its Paleolithic human and animal remains.
|
E2028511
|
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: Istállós-kő Cave | Statement: [Bükk National Park, contains, Istállós-kő Cave]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Istállós-kő Cave Triple: [Bükk National Park, contains, Istállós-kő Cave]
Generated description
Istállós-kő Cave is a notable prehistoric cave and archaeological site in Hungary’s Bükk Mountains, renowned for its Paleolithic human and animal remains.
Provenance (5 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d09e671081909a10136a8db8a005 |
completed | May 3, 2026, 4:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c69978d08190acd871e2e3ce7b1b |
completed | June 19, 2026, 4:33 a.m. |
| NEDg | Description generation | batch_6a34c8226bac81909eed319bf6b97197 |
completed | June 19, 2026, 4:40 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a34c9336fc4819092f2682493a94cfe |
completed | June 19, 2026, 4:44 a.m. |
Created at: May 1, 2026, 1:19 a.m.