Triple

T34839931
Position Surface form Disambiguated ID Type / Status
Subject Mylasians E1004312 entity
Predicate regionallyImportantCity P118397 FINISHED
Object Mylasa 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: Mylasa | Statement: [Mylasians, regionallyImportantCity, Mylasa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionallyImportantCity
Context triple: [Mylasians, regionallyImportantCity, Mylasa]
  • A. majorTownInRegion chosen
    Indicates that a town is one of the principal or most significant towns within a specified region.
  • B. servesAsFocusCityFor
    Indicates that a city functions as a primary or designated focus city for an airline, organization, or transportation network, typically hosting significant but not hub-level operations or activities.
  • C. capitalCityOfRegion
    Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
  • D. capitalOrMajorCenter
    Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
  • E. otherMajorCity
    Indicates that one city is another major city associated with or comparable in importance or status to the first city.
  • F. None of above.

Provenance (3 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_69f76db97714819099b5bed36fd64e9d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff9a25407c81909faa86e72a7a9d17 completed May 9, 2026, 8:33 p.m.
PD Predicate disambiguation batch_69ff99c613688190a03b2f93d5ccad2b completed May 9, 2026, 8:32 p.m.
Created at: May 3, 2026, 4 p.m.