Triple
T29970208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mun of Balhae |
E761294
|
entity |
| Predicate | sentEmissariesTo |
P94623
|
FINISHED |
| Object | Tang dynasty |
—
|
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: Tang dynasty | Statement: [King Mun of Balhae, sentEmissariesTo, Tang dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentEmissariesTo Context triple: [King Mun of Balhae, sentEmissariesTo, Tang dynasty]
-
A.
sentMissionTo
Indicates that one entity dispatched or assigned another entity to carry out a specific mission at a particular destination or context.
-
B.
sentEmbassyTo
chosen
Indicates that one entity dispatched an official diplomatic mission or embassy to another entity.
-
C.
sentMessengersTo
Indicates that one entity dispatched or directed messengers to another entity or location for communication or representation.
-
D.
sentMembersTo
Indicates that one entity dispatched or assigned its members to another entity or location.
-
E.
sentOnMissionWith
Indicates that one entity was assigned or dispatched to a mission together with another entity as companions or teammates.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786d6e108190b7f631c222899519 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:31 p.m.