Triple
T20099526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Munmu |
E496495
|
entity |
| Predicate | usedAllianceWith |
P11884
|
FINISHED |
| Object | Tang dynasty to defeat rival kingdoms |
—
|
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: Tang dynasty to defeat rival kingdoms | Statement: [King Munmu, usedAllianceWith, Tang dynasty to defeat rival kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAllianceWith Context triple: [King Munmu, usedAllianceWith, Tang dynasty to defeat rival kingdoms]
-
A.
allianceUse
chosen
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
-
B.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
C.
appliedInAlliance
Indicates that something (such as a method, strategy, or resource) is used or implemented within the context of an alliance or partnership between parties.
-
D.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
E.
involvesAlliance
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666f2298819089659f13556ca305 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:26 p.m.