Triple

T28946455
Position Surface form Disambiguated ID Type / Status
Subject Larut, Matang and Selama District E730592 entity
Predicate includesArea P1393 FINISHED
Object Larut
Larut is a historical area in the state of Perak, Malaysia, once known for its rich tin-mining activities and now forming part of the Larut, Matang and Selama District.
E1842382 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: Larut | Statement: [Larut, Matang and Selama District, includesArea, Larut]
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: Larut
Triple: [Larut, Matang and Selama District, includesArea, Larut]
Generated description
Larut is a historical area in the state of Perak, Malaysia, once known for its rich tin-mining activities and now forming part of the Larut, Matang and Selama District.

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_69f043ea0aa88190a25acbf46157995a completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f65b8710908190b3746b9a711484b3 completed May 2, 2026, 8:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24ec47e9088190b2513ab7d68f3b9d completed June 7, 2026, 3:58 a.m.
NEDg Description generation batch_6a24f07e3a54819090dc0d92cee92204 completed June 7, 2026, 4:15 a.m.
NED2 Entity disambiguation (via description) batch_6a24f56a17a48190a309ea59a2ebf4d1 completed June 7, 2026, 4:36 a.m.
Created at: April 28, 2026, 8:40 a.m.