Triple

T11150119
Position Surface form Disambiguated ID Type / Status
Subject Jordanian diplomatic missions E263761 entity
Predicate typeOfEmbassy P13280 FINISHED
Object bilateral embassy LITERAL 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: bilateral embassy | Statement: [Jordanian diplomatic missions, typeOfEmbassy, bilateral embassy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfEmbassy
Context triple: [Jordanian diplomatic missions, typeOfEmbassy, bilateral embassy]
  • A. diplomaticMissionType chosen
    Indicates the specific category or nature of a diplomatic mission that characterizes the relationship between the sending and receiving entities.
  • B. relationshipToEmbassy
    Indicates the type of formal or personal connection an entity has with a specific embassy.
  • C. hasConsulateOfUnitedStatesIn
    Indicates that a consulate of the United States is located in the specified place.
  • D. diplomaticTool
    Indicates the use of an object, method, or channel as a means or instrument for conducting diplomatic relations or negotiations between parties.
  • E. hasDiplomaticMission
    Indicates that one entity maintains an official diplomatic representation, such as an embassy or mission, in the territory or jurisdiction of another entity.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8701ea481908c86c2359f5dc957 completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75ce71944819089eee9b5c9283cbd completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:28 p.m.