Triple
T323921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Communist Party |
E6471
|
entity |
| Predicate | inPowerSince |
P12797
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Chinese Communist Party, inPowerSince, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPowerSince Context triple: [Chinese Communist Party, inPowerSince, 1949]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
regainedPowerIn
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
C.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
D.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e949364c8190bc2351f5413f5057 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eb18bda48190ac3d96a61a6a684d |
completed | Feb. 28, 2026, 1:18 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.