Triple
T37528810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of China in the United Kingdom |
E932977
|
entity |
| Predicate | headOfMissionStart |
P188206
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Embassy of China in the United Kingdom, headOfMissionStart, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfMissionStart Context triple: [Embassy of China in the United Kingdom, headOfMissionStart, 2021]
-
A.
headOfMission
Indicates that one entity serves as the chief or principal leader in charge of a specific mission or delegation.
-
B.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
C.
firstMissionCommander
Indicates that the subject served as the commander of the object's first mission.
-
D.
launchOnMission
Indicates initiating the sending of an entity (typically a vehicle, spacecraft, or device) to carry out a specific mission or operation.
-
E.
overseesMission
Indicates that one entity has responsibility for supervising, directing, or managing the execution of a mission undertaken by another entity.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.