Triple
T28481650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Wuling of Zhao |
E720707
|
entity |
| Predicate | significantCampaign |
P4656
|
FINISHED |
| Object | campaigns against Linhu |
—
|
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: campaigns against Linhu | Statement: [King Wuling of Zhao, significantCampaign, campaigns against Linhu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantCampaign Context triple: [King Wuling of Zhao, significantCampaign, campaigns against Linhu]
-
A.
notableCampaign
chosen
Indicates that an entity is prominently associated with a particular campaign, such as by leading, featuring in, or being a key focus of that campaign.
-
B.
majorCampaignType
Indicates the primary category or classification of a campaign within a broader set of campaign types.
-
C.
hasMajorCampaign
Indicates that an entity is associated with or participates in a primary, large-scale campaign.
-
D.
notableCampaignDirection
Indicates that an entity played a significant role in directing or guiding a particular campaign.
-
E.
continuedCampaignsOf
Indicates that one campaign is a direct continuation or follow-up of another campaign, extending its efforts or objectives over time.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 2:55 a.m.