Triple
T23797430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korean embassies |
E588575
|
entity |
| Predicate | includesEmbassyIn |
P98893
|
FINISHED |
| Object | Beijing, China |
—
|
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: Beijing, China | Statement: [North Korean embassies, includesEmbassyIn, Beijing, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEmbassyIn Context triple: [North Korean embassies, includesEmbassyIn, Beijing, China]
-
A.
hasConsulateOfUnitedStatesIn
Indicates that a consulate of the United States is located in the specified place.
-
B.
hasDiplomaticMission
Indicates that one entity maintains an official diplomatic representation, such as an embassy or mission, in the territory or jurisdiction of another entity.
-
C.
isLocatedInDiplomaticQuarter
Indicates that one entity is situated within or belongs to the designated diplomatic quarter area.
-
D.
relationshipToEmbassy
Indicates the type of formal or personal connection an entity has with a specific embassy.
-
E.
diplomaticMissionInCity
chosen
Indicates that a diplomatic mission (such as an embassy or consulate) is located in or operates within a specific 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6ddc2d88190b6124d9fb2695d24 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:50 p.m.