Triple

T37318210
Position Surface form Disambiguated ID Type / Status
Subject Ancient City E926396 entity
Predicate alsoKnownAs P39 FINISHED
Object Muang Boran
Muang Boran is a vast open-air museum in Samut Prakan, Thailand, featuring scaled-down replicas of the country’s most significant historical sites and traditional architecture.
E2232273 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: Muang Boran | Statement: [Ancient City, alsoKnownAs, Muang Boran]
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: Muang Boran
Triple: [Ancient City, alsoKnownAs, Muang Boran]
Generated description
Muang Boran is a vast open-air museum in Samut Prakan, Thailand, featuring scaled-down replicas of the country’s most significant historical sites and traditional architecture.

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_69f76eb28af88190b093b32e3fd614ab completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb5b3d32b881908527f8a545116b22 completed May 6, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a409eed292c81908c6d5b4e7783f83a completed June 28, 2026, 4:11 a.m.
NEDg Description generation batch_6a40a01b09b48190afb806ca4774f38c completed June 28, 2026, 4:16 a.m.
NED2 Entity disambiguation (via description) batch_6a40a0e074b88190b18ca46f62fc371e completed June 28, 2026, 4:19 a.m.
Created at: May 3, 2026, 4:16 p.m.