Triple
T2944988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongguang Emperor |
E79478
|
entity |
| Predicate | loyalistsBase |
P44132
|
FINISHED |
| Object | lower Yangtze region |
—
|
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: lower Yangtze region | Statement: [Hongguang Emperor, loyalistsBase, lower Yangtze region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyalistsBase Context triple: [Hongguang Emperor, loyalistsBase, lower Yangtze region]
-
A.
loyalistUnitOf
Indicates that one unit is a loyal or devoted supporter, follower, or subordinate of another entity.
-
B.
RoyalistSide
Indicates that an entity is aligned with, supports, or belongs to the faction favoring a monarchy or royal authority in a given conflict or context.
-
C.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
D.
royalistObjective
Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
-
E.
rebelInstitution
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
- F. None of above. chosen
Provenance (4 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b2752481908ec6f9a9cc24c0a7 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:56 p.m.