Triple

T25343161
Position Surface form Disambiguated ID Type / Status
Subject Wind Cave (Mulu) E635469 entity
Predicate hasNearbyAttraction P2064 FINISHED
Object Deer Cave (Mulu)
Deer Cave (Mulu) is a vast show cave in Gunung Mulu National Park in Malaysian Borneo, renowned for its enormous main chamber and spectacular daily bat exodus.
E1684306 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: Deer Cave (Mulu) | Statement: [Wind Cave (Mulu), hasNearbyAttraction, Deer Cave (Mulu)]
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: Deer Cave (Mulu)
Triple: [Wind Cave (Mulu), hasNearbyAttraction, Deer Cave (Mulu)]
Generated description
Deer Cave (Mulu) is a vast show cave in Gunung Mulu National Park in Malaysian Borneo, renowned for its enormous main chamber and spectacular daily bat exodus.

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_69e75a99bd6481909476115b35b9a8e4 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f498b936f08190b750199798e9effc completed May 1, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad4bee908190ae8ade61dee1e242 completed May 22, 2026, 7:23 p.m.
NEDg Description generation batch_6a10ae56b8a48190a448e1a4bd938a2b completed May 22, 2026, 7:28 p.m.
NED2 Entity disambiguation (via description) batch_6a10af25783081908b2c79210eb97fc1 completed May 22, 2026, 7:31 p.m.
Created at: April 21, 2026, 1:32 p.m.