Triple
T32508166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wu Guang |
E830856
|
entity |
| Predicate | partnerInRebellionWith |
P120310
|
FINISHED |
| Object | Chen Sheng |
—
|
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: Chen Sheng | Statement: [Wu Guang, partnerInRebellionWith, Chen Sheng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInRebellionWith Context triple: [Wu Guang, partnerInRebellionWith, Chen Sheng]
-
A.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
B.
associatedRebellion
chosen
Indicates a relationship where an entity is linked to, involved in, or connected with a particular rebellion or uprising.
-
C.
associatedWithRebelGroup
Indicates that one entity is connected or linked in some capacity to a rebel group, such as through membership, support, collaboration, or affiliation.
-
D.
partnerInBattle
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
-
E.
partnerInReformWith
Indicates that two entities collaborate as partners in carrying out or supporting a reform effort.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1 a.m.