Triple

T30034474
Position Surface form Disambiguated ID Type / Status
Subject Philippine–United States relations E763115 entity
Predicate PhilippinesEmbassyLocationInUnitedStates P168372 FINISHED
Object Washington, D.C. 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: Washington, D.C. | Statement: [Philippine–United States relations, PhilippinesEmbassyLocationInUnitedStates, Washington, D.C.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: PhilippinesEmbassyLocationInUnitedStates
Context triple: [Philippine–United States relations, PhilippinesEmbassyLocationInUnitedStates, Washington, D.C.]
  • A. USEmbassyLocation
    Indicates that a specified location is the site where the United States embassy for a particular country is situated.
  • B. embassyOfUnitedStatesLocation
    Indicates the geographic location where a particular United States embassy is situated.
  • C. U.S.EmbassyLocation
    Indicates the location where a U.S. embassy is situated or hosted.
  • D. hasConsulateOfUnitedStatesIn
    Indicates that a consulate of the United States is located in the specified place.
  • E. capitalOfUSMissionLocation
    Indicates that a location serves as the capital city where a particular U.S. mission (such as an embassy or diplomatic post) is situated.
  • F. None of above. chosen

Provenance (4 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_69f2246fb2b88190acff36bf7975c8f0 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f679d37ea4819096dd4a2352798748 completed May 2, 2026, 10:25 p.m.
PD Predicate disambiguation batch_69f66ec9919881908a187bfc7c4df192 completed May 2, 2026, 9:38 p.m.
PDg Predicate description generation batch_69f67256d064819094be04fc1bbbc635 completed May 2, 2026, 9:53 p.m.
Created at: April 29, 2026, 6:50 p.m.