Triple

T19031381
Position Surface form Disambiguated ID Type / Status
Subject Christmas Capital of the Philippines E465746 entity
Predicate mainSymbol P18980 FINISHED
Object parol 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: parol | Statement: [Christmas Capital of the Philippines, mainSymbol, parol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: parol
Context triple: [Christmas Capital of the Philippines, mainSymbol, parol]
  • A. parol chosen
    A parol is a traditional Filipino ornamental lantern, typically star-shaped and brightly illuminated, prominently featured during Christmas celebrations.
  • B. Par
    Par is a shortened variant of the surname "Parr," commonly used as a family name in various cultures.
  • C. Parola
    Parola is a small town in Maharashtra, India, known for its historical fort and location within the Jalgaon district.
  • D. Parl
    Parl is the commonly used abbreviation for the Parliament of Singapore, the country's unicameral legislative body.
  • E. Parap
    Parap is an inner-city suburb of Darwin in Australia's Northern Territory, known for its popular weekend markets and tropical, laid-back atmosphere.
  • 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_69d8dd0359648190bc2a9202c5cf29d2 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d7404d748190bcb51692fb822fd4 completed April 20, 2026, 7:35 a.m.
Created at: April 10, 2026, 12:02 p.m.