Triple

T22861693
Position Surface form Disambiguated ID Type / Status
Subject Plaosan Temple E566938 entity
Predicate hasPart P35 FINISHED
Object Plaosan Lor 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: Plaosan Lor | Statement: [Plaosan Temple, hasPart, Plaosan Lor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Plaosan Lor
Context triple: [Plaosan Temple, hasPart, Plaosan Lor]
  • A. Plaosan Lor chosen
    Plaosan Lor is one of the twin 9th-century Buddhist temple groups in the Plaosan complex near Prambanan, Central Java, notable for its intricate reliefs and blend of Hindu-Buddhist architectural styles.
  • B. Balasagun
    Balasagun was a prominent medieval Central Asian city in the Chüy Valley, historically significant as a political and cultural center along the Silk Road.
  • C. Lanahan
    Lanahan is a surname most notably associated with American lawyer and politician Samuel Jackson Lanahan.
  • D. Lodoselo
    Lodoselo is a small village in the municipality of Sarreaus, in the province of Ourense, Galicia, Spain.
  • E. Pelantaro
    Pelantaro was a prominent Mapuche military leader who played a key role in resisting Spanish colonial forces during the Arauco War in Chile.
  • 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_69e24589083081908d5694c4fdc80086 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17efcc1308190a95d10e431295ca2 completed April 29, 2026, 3:46 a.m.
Created at: April 17, 2026, 3:37 p.m.