Triple
T31986292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuan Shao |
E816731
|
entity |
| Predicate | ledCoalitionAgainst |
P83371
|
FINISHED |
| Object | Dong Zhuo |
—
|
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: Dong Zhuo | Statement: [Yuan Shao, ledCoalitionAgainst, Dong Zhuo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledCoalitionAgainst Context triple: [Yuan Shao, ledCoalitionAgainst, Dong Zhuo]
-
A.
coalitionLed
chosen
Indicates that one entity serves as the primary leader or organizer of a coalition composed of multiple entities.
-
B.
ledAgainst
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
-
C.
loserCoalition
Indicates a coalition of entities that collectively fail to win or achieve a desired outcome in a competitive or decision-making context.
-
D.
coalitionBase
Indicates that one entity serves as the foundational or primary support group upon which a broader coalition or alliance is built.
-
E.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:12 a.m.